> Yeah, it's got that disease where last week's code doesn't work this week.

That's called idiots using the nightly compiler because Consume Feature And Get Excited For Next Feature.

My oldest Rust code is from 2021 and I do get deprecation warnings on some feature used in some library I forked, but I've never had to change Rust code because of a compiler upgrade.

The situation in C is actually somewhat worse, because every new version the GCC developers roll out some clever new warning. Normally this shouldn't matter, but in reality -Werror does trickle into codebases and then GCC makes an update and code stops compiling.

The other thing GCC devs like to do is invent clever new optimizations which turn undefined behavior that works into undefined behavior that crashes. Insert obligatory smuggy_just_write_valid_c.png, but since All Non-Trivial Code Has Bugs, this does end up being a language change (also, people with bosses and deadlines HATE smuggy_just_write_valid_c.png).

Anyway, I'm not really a language-warrior, I've invested a lot of time in learning Rust so I'm definitely talking my book, but really what I'm trying to say is I think Rust will continue to grow and C will not.