And it's unsuited for many roles because it has eschewed reverse compatibility. Sure, you can write an operating system in Rust, but you'll have to re-write it (and possibly introduce new bugs) in five years or so.
I'm not the world's biggest C fan, but there are programs I wrote in the late 70s that still compile and do what you think they should do.
This is one of the good things about C. I could write something in C99 and, in 10 years, it will likely still compile without changes!
Can we say this about Java, C#, D.. and ESPECIALLY Rust??? You might still be able to download the specific version, but you then have to cater to package manageers, or the IDE/editor you are using, etc.
C does not try to cram in "Cool Feature A" and "Cool Feature B" because it is the cool thing of the time.
I think the only other languages to come close is Odin and, perhaps, Zig. Both have not had a production release (yet) so I am still expecting there to be some changes at this point. However, once mature, I would expect very little changes if left for 10 years. Of course - they are young languages but Odin (especially) makes it very clear what they will and won't add to the language, and keeps it pretty close to C in a number of ways.
I think you could say this about Java. The others, I'm unsure about.
This is not entirely the case for C. I guess.. it depends.
If I use gcc (std=c99) for a project I wrote today... this will likely work in 10 years time, with the latest gcc version... without changes.
It's the same with Java, where to compile old applications you also need to use the same JDK version, however with Java it's a bit harder cause there is no file that says which JDK version should be used to compile this. At least I think so, correct me if I'm wrong.
That's okay. Most rust devs get an erection at the idea of rewriting a massive codebase. For them the required rewrite every 5 years is a feature, not a bug.