and that is a problem because? These are funded by tax dollars collected. It's impossible for people to stop paying for them whether they make sense or not.

The "memory safety" of rust is oversold since "safety" is not formally proven for the rust language. While anecdotally memory-related bugs seem less likely, rust without unsafe is not absolutely safe.

One person having "god-mode" access isn't usually that terrible.

The article solves the cpu spike by disabling the io or memory controller, but if one would like to use those controllers, a better way to charge memory would be nice.

It is unfortunate that it's clear where the memory should be charged, but the kernel does not provide reliable way to deterministically charge that memory. If anyone has any design ideas, please feel free to chime in!

[1] https://github.com/nix-community/nix-ld [2] https://github.com/Mic92/envfs

The blog post linked by [1] is quite good.

Supporting multiple page sizes well transparently is non-trivial.

For a recent summary on one of the approaches, TAO (THP Allocation Optimization), see this lwn article: https://lwn.net/Articles/974636/

Which I find deeply confusing as these precisely correlate with QoL compared to life 100 years ago. E.g. the air conditioner was just invented and way more expensive 100 years ago. With the attitude of "as successful as its least privileged soul", I doubt the air conditioner would be nearly as available today.

I suppose it shows who's paying Mozilla.

But a more common scenario is the phone gets used for parts. As for the icloud account. AFAIK you used to be able to get the full account email with GSX. Not sure about now.