

Rust is already in the kernel and Torvalds wants more, faster. He’s being obstructed by C purists, who at this point are the people who should fork the kernel if they see anything but C as heresy.
Rust is already in the kernel and Torvalds wants more, faster. He’s being obstructed by C purists, who at this point are the people who should fork the kernel if they see anything but C as heresy.
One rather obvious reason is that society has a lot of greybeards in general. The baby boomer generation was named that for a reason, and people have been living longer on average. Lots of countries are struggling with the demographic effects. There’s no reason to expect that tech or something even more specific like FOSS would be exempt.
Another aspect here is that FOSS is still kind of new in society. There’s just more people who have had the chance to age into FOSS greybeards than when those greybeards were young. (And they were thus likely to a lesser degree blocked by entrenched greybeards when they were getting started.)
Thing is, there is already Rust in Linux, and Torvalds wants more, faster. He’s being sabotaged by C purists, who at this point should stop acting unprofessionally, or at the very least make their own “only C” fork if they disagree with his leadership so much.
>What is C++? A miserable huge pile of "should"s
TIOBE literally ranks languages by search results. It’s at best a measure of SEO. It is, generally, a trash metric that shouldn’t be used for anything.
Reads more like if you made a mess as a kid and cleaned up before your parents came home. The state between when they leave and when they arrive is up for experimentation.
Leaking isn’t really the issue, though I suppose Rust helps with that as well. Its memory sales pitch is more about memory safety, which is not reading or writing the wrong parts of memory. Doing that can have all sorts of effects, where the best you can hope for is a crash, but it often results in arbitrary execution vulnerabilities. Memory _un_safety is pretty rare and most prominent in languages like C, C++ and Zig.
Rust also has more information contained in it, which means resulting programs can actually be faster than C, as the optimizer in the compiler is better informed.