I remember using it all the time for the Windows headers because they pollutes the compilation unit like you wouldn't believe — the rule was to only include them in c/cpp files.

That's kind of a hack, still best only used in implementation files, not headers.

The irony is that including/using many standard c++ headers is far far more expensive than including a lean windows.h these days.

To make hobby-coding fun, i use a mstdp.hpp that implements "naive" versions of unique,shared,function,etc that compiles faster than including just one of the std versions (and yes, MSVC versions of those libraries seem to be excessivly complex).

Not when using modules, which I have moved into on hobby projects.

The import std is much faster than plain #include<iostream>.

This is a fair point. Last time I tried modules in anger, it wasn't viable. Cmake didn't support them (well, they were experimental), intellisense didn't work and there were many ICE's in MSVC.

Maybe it's time to move my hobby project over and see how well it works.

I give you that Intelisense is broken as always, and the best experience appears to be with Clion, but I can live with it.

Best experience is VC++ with MSBuild, cmake/ninja work great with latest clang however import std support is not yet enabled by default in CMake.

I only care about VC++ for hobby coding, hence using modules.

See for example, https://github.com/pjmlp/RaytracingWeekend-CPP

I've just spent an hour trying to set up import std to use std::print on MacOS. I got there, eventually with cmake + ninja. I hit an absolutely ludicrious number of errors for effectively a hello world, and I don't understand why in 2026 it is as complicated as it is.

But, no ICEs and it's working! I'll start writing some code with them tomorrow.

That may be true, but it's a "hack" that has caused me approximately 1 issue in 15 years of writing C++ professionally, and that issue was a problem with our build system not the precompiled header.

> Still best only used in implementation files, not headers.

We only compile implementation files!

I’m not entirely convinced, there are many dimensions to progress. For example, DeepSeek has had a few very impressive innovations that all models could benefit from. There’s also the law of diminishing returns, the US labs have plenty of CAPEX already.

Sometimes, constraints, like sanctions, can also be a source if innovation.

How is /e/ less open than Graphene? As far as I understand, they are both pretty open minus firmware that they can't control?

I'm actually curious if there's something I don't know about /e/

Others explained it in this thread already

I'm also on Emacs and Niri, seems to be a popular combo, and I don't have any performance problem.

At home I'm driving an Ultrawide (3440x1440@75Hz) at scale 1.1.

At work I'm driving two 4k screens at scale 1.2.

I might be less sensitive to latency but it could also be a graphics driver issue or something similar. I'm using Arch with emacs-wayland (pgtk) with a strix halo (all AMD) laptop.

It might also just be the case that the hardware you have is good enough that the lag isn't noticable.

You should still be able to notice a spike in CPU usage whenever you force Emacs to redraw the frame by typing into it though.

People are paranoid that everything they read was written by a LLM. It's likely that they are even more suspicious because you used one to code.

You should be proud of both the work you did and the article :-).

The sales are a nice thing but for me the biggest benefit of Steam is knowing that I can use my games library on other/future devices.

My games have been working on my desktop from 10 years ago, the SteamDeck, my laptop and likely any future computer I buy that runs Linux.

Why a team... give me a few days ;-)

I'm using a Strix Halo laptop (~3k, 64GiB) and with Gemma 4 and Qwen 3.6, both at 8 bits, I'm seeing very impressive results.

As a work tool, this is reasonably priced. You can save a bit of money by opting for a non-laptop form factor.

It only reversed it for within the US, I learned that when the company I worked for (owner was a US company) closed.

Right, you can only deduct R&D expenses that happen inside the U.S.

If you want to do R&D overseas, best to set up an overseas company.

I think the grandparent references many referendums that rejected EU treaties:

- Maastricht Treaty, 1992, Denmark, - European Constitution, 2005, France and Netherlands, - Lisbon Treaty, 2008, Ireland.

The votes were usually redone and passed. The exception is Norway which refused to join twice.

> Clearly not everyone loves the EU but the majorities are very much in favour (and certainly this is the case among the people who actually understand politics, economics, etc.).

This is quite the loaded statement. I've heard from people on either both sides of the argument that understood politics and economics very well (professors, lecturers, etc.)

It's always interesting to see accounts popping up in this thread trying to delegitimize EU and spew out bunch of vague misleading statements against it.

Why is that? Which EU citizen protection is angering you? :)

Nothing of that is angering me, I live in the EU and life is pretty nice.

My comment above was meant to provide context and to point out that both sides of the argument can be legitimate.

The comment is neutral, you shouldn't be able to infer what I think about the EU from it. It simply points out facts and says that reducing a point of view to being uninformed is too easy.

My stance on the EU is complex: it does good, it does bad, it affects each member states differently, it changes over time. Those are all pretty neutral statements too, only siths live in extremes ;-).