MFHava

Don't be sad for them. AFAIK those that didn't retire are now at Nvidia - hopefully continuing to improve the frontend...

No idea what you are talking about, I need none of the apps you mention...

>> The current contracts are not good enough for anybody who wants them - > This is a recurring pattern across large changes to c++. Modules and coroutines both are great examples of this.

Coroutines are ready since C++20, there is some stuff missing in the language (`for co_await` being the most obvious thing), but the feature is useful as is...

> And I think each national body has a veto. (that is the vote has to be unanimous, but not sure here).

No veto. Every P-member has a vote (abstain/approve/disapprove). Whether C++26 gets published is decided by numerical consensus.

Oh it was, actually still is - our right wing party is still talking about this stuff regularly...

> They then watched the gcc community work through 10 years of pain to make the transition.

During the same time the MSVC compiler broke ABI multiple times and the world didn't end.

The fact that breaking ABI was such a shitshow for libstc++ is more related to the way C++/ABI/SOs is/are handled in Linux...

I have to disagree with the author in one key detail: IMHO Windows wasn't neglected, it was actively made worse over the last decade(s)...

> no one is even buying idTech

Kinda hard to buy an engine that is not for sale...

> Most crucially, both keyboards introduced a new tenant: Control (⌃). This was modifier key number four, and to this day, I don’t fully understand why ⌘ wasn’t repurposed here

Because then we would have ended up with the same mess that is Windows (and Linux for that matter) when it comes to ^C being ambiguous...