At the very least we need _current_ models, though. The weights have all sorts of information baked into them, like "how do Python unit test drivers work" or "what does idiomatic C# look like," that will just naturally go stale over time as the frameworks improve. In five years, Qwen 3.8 will still be targeting the Python of 2026.
Why do we need Rust, for instance, when LLMs know how to use C++ without shooting themselves in the foot? If that's not entirely true today, it certainly will be tomorrow.
See also the lack of new instruction-set architectures in the CPU business. Why do we need more, in the absence of fundamental and revolutionary hardware innovations? Even RISC-V is just a rehash of MIPS.
I.e. I think you can bake certain properties into the language such that various kinds of static checks can prevent certain types of errors. This should make the language nicer for coding without reading any of the code.
An LLM doesn't need a memory-safe language. It needs one it knows like the back of its metal hand.