That's crazy, I haven't seen any other system that really tries to do that.
- cargo-anneal - VeriFast - RefinedRust - safety-tags - Verus
These 5 use very different mechanisms. This is still a very active research area.
https://github.com/google/rust-skills/blob/main/unsafe_rust_...
(I qualify with “in a sane world” because obviously it could happen. In a truly sane world, JavaScript would never have happened, either!)
I’d counter with: as LLM driven coding becomes more and more common the PITA borrow checker is something individual developers interact with less than less. Garbage collection looks more and more like a waste when an LLM can examine memory allocations before the app is even built.
Just because they did in the past doesn't mean they will continue to do so in the future. If we are honest then Moore's Law ended a decade ago (the latest) and we've been picking the low hanging fruit we left alone during Moore's era since. This too will come to an end for sure, just not a pretty and well defined one.
So, my conclusion is the opposite. Garbage collected and DX optimized languages made sense while processors and memory got faster, the future will be elsewhere.
And yeah, it feels a bit like JavaScript a while ago, that's a good comparison.