Rust and Go haven't been around long enough to make those statements about them.
https://timidger.github.io/posts/i-cant-keep-up-with-idiomat...
there are other similar complaints around the net.
While the C and C++ code I wrote over 2 decades ago is now finally "out of date" as of 5 years ago. It took a while. Not 2-3 years.
Which is absolutely attributed to the language being new, not a design fault.
C is already "settled"
I've been able to compile and run C and C++ code from 20 years ago a truly amazing number of times. It's really surprising at how easy it is to work with well written code even if it's decades old.
Will Rust and Go age that way? Maybe. Too soon to tell.
Not if you have used any third party libraries. Dependency management is a nightmare in these languages.
I spend most of my time working deep in the internals of some things that are 10+ years old running even older versions of some highly (and often badly) modified linux kernels. The well written C/C++ projects definitely stand out.
Of those who do like Common Lisp, many like it because the standard hasn't changed in nearly thirty years (while simultaneously offering features added to the C++ standard just very recently, e.g. a filesystem path abstraction).