Solaris in SPARC is the only production UNIX with hardware memory tagging.

Something that some security conscious folks care about.

Does OpenBSD not do that? That feels like something OpenBSD could do, given their near paranoid level of exploit reduction and theos hardon for SPARC

I use modules in all my private projects since the last two years.

The C++ WG is like any other open source project, even when it doesn't look like it.

Someone has to bring a written spec to WG21 meetings and push it through.

And like in every open source project that doesn't go the way we like, the work is only done by those that show up.

> The C++ WG is like any other open source project, even when it doesn't look like it.

In many ways, it isn't.

> Someone has to bring a written spec to WG21 meetings and push it through.

That is one way it is not like (most) other FOSS projects. In a typical FOSS project, there are bug reports and feature/change requests that people file. They don't have to write a full article merely for their idea to be given the time of day. Certainly not have to appear physically at meetings held elsewhere in the world. Of course, the question of the extent to which ideas and requests from the public are considered seriously and fairly is a spectrum - some FOSS projects give them more attention and consider them seriously, others do not. vis-a-vis WG21 the "public" is, to some extent: Compiler author teams, standard library author teams, national bodies, and large corporations using C++. This is perhaps not entirely avoidable, since there are millions of C++ users, but still.

Anyway, what I described isn't just some personal ideas of mine, it is for the most part ideas which have been put forward before the committee, either directly in submitted papers or indirectly via public discussion in fora the committee is aware of.

They kind of do, otherwise those RFC, PIP, TIP, PEP, JSR,... die out.

A pull request isn't enough, even if online collaboration is simpler than with ISO related meetings.

Those are examples of standardization processes, not FOSS projects.

Used by programming languages FOSS projects.

NVidia is the main sponsor of this kind of work, and a few key figures are nowadays on their payroll.

Usable enough for Office, and the initial proposal was done by Microsoft.

It has the developer mindshare of game engines, games and VFX industry standards, CUDA, SYCL, ROCm, HIP, Khronos APIS, game consoles SDK, HFT, HPC, research labs like CERN, Fermilab,...

Ah, and the two compiler major frameworks that all those C++ wannabe replacements use as their backend.

With people still paying to get the compiler, https://www.eiffel.com

Except people keep forgetting they implement the standards on their very foundation.

Yet the WebAssembly bros are into replicating application servers with Kubernetes pods running WebAssembly containers, go figure.

I know right? Who wants sub-millisecond readiness, sub-second image replication and a measly couple of megs worth of memory alloc per service when everyone can just get themselves a 2 gig springboot heap by default?

FWIW Wasm is hitting kubernetes because that's what customers are explicitly asking for, and the majority of enterprise Wasm-on-k8s afopters are doing so precisely because they want to eradicate Spring bloat and the associated supply chain risks from their engineering orgs.

There are plenty of supply chain attacks without Spring into the picture.

Also, are you sure you are talking about Kubernetes performance over there?

Plenty of examples on Github, Microsoft has talks on how Office has migrated to modules, and the Vulkan updated tutorials from Khronos, have an optional learning path with modules.