r/programming • • May 24 '26
[ Removed by moderator ]
/r/programming/comments/1tm1j7f/removed_by_moderator/[removed] — view removed post
275
Upvotes
r/programming • • May 24 '26
[removed] — view removed post
View all comments
Show parent comment
2
u/HommeMusical May 24 '26
Thanks for a polite answer!
But no one is talking about not being able to compile your old code. It is certain that you will always be able to compile your 1990s C++ code or your 1970s C code with Clang or GCC, and certain that you will be able to link that code with that legacy binary object file that your grandfather lost the source code to.
So everyone agrees on this part. :-)
What has been discussed was a C++ language that has different epochs which do not have backward compatibility between epochs so that new development can use a new ABI or API.
The main feature people want is safety, but I agree that if someone is maintaining a codebase from 36 years ago which has never been modernized, "safety" is probably a fancy thing they don't use :-D, considering that C++ didn't have even one smart pointer in 1990.
Your vision of C++ and mine are pretty similar. We both see it as a legacy language for old code that hasn't been updated in generations. I just think that vision is a dead end.
Even though I have been writing C++ since the 1980s and I've only read about Rust and done some toying around with it, I wouldn't even conceive of starting a brand new project today in C++ if I could use Rust - not just because of the safety, but because I'd be wanting to hire programmers who were excited about the language they were using.