Remove the need to, yes. Remove the ability to? No, and rust doesn’t prevent you from doing that, it just makes you mark it unsafe so that way if you fuck up and cause a memory error, the root cause can be narrowed down to a tiny fragment of the code base.

Unsafe rust has proven that it can be an effective alternative here, ideal especially when the consumers are also rust.

If it ain’t broken, don’t fix it.

That’s the thing, it is broken and there is a fix desperately needed. C lacks memory safety, which is responsible for many, many security vulnerabilities. And they’re entirely avoidable.

What exactly are the hazards of shared memory and locks? The ownership system and the borrow checker do a pretty good job at enforcing correct usage, and if you are clever you can even guarantee no deadlocks (talk at rustconf 2024 about the fuchsia network stack).

In what way has Microsoft enshittified GitHub? Since the acquisition they’ve mostly made more services free for open source users, and prices and features haven’t gotten more restrictive.