•

The empire of C++ strikes back with Safe C++ blueprint

https://www.theregister.com/2024/09/16/safe_c_plusplus/

You pipsqueaks want memory safety? We'll show you memory safety! We'll borrow that borrow checker

The empire of C++ strikes back with Safe C++ blueprint

•

I think, the idea was along the lines of "because C++ was not memory-safe, and it has to stay compatible with how it was, there are still a lot of ways to not write memory-safely"

This makes sense, there are memory-safely features available but there are a lot of programmers that will never willingly use that features, because the olden ways are surely better

Other than that, I agree, when you're paid to fix an unfixable problem you will probably claim something like that and advocate for your solution being the only one that solves this

0x0

•

there are a lot of programmers that will never willingly use that features, because the olden ways are surely better

Found the rust shill.

sukhmel

•

If you want everyone to stop trying to shove Rust everywhere, just use smart pointers more. I may somehow get over Rust not replacing every other language if those languages will be safe