Let's also admit every language before Rust hasn't succeeded at out right replacing the vast majority of C/C++, so it becomes it's own form of conservatism/bias. This post is coming from one of the few companies that actually does complete large scale rewrites of things. I'm curious/excited to see how it goes for them.
And I have that C/C++ bias: I don't enjoy programming in rust as much as I do C, but I don't like doing lots of new things.
> Let's also admit every language before Rust hasn't succeeded at out right replacing the vast majority of C/C++,
Many languages expelled C/C++ from the domains they were once kings of entirely. It used to be "the language" for many, many things.
There is hardly that much C and C++ left on GUI frameworks and distributed computing, other than existing infrastructure from projects that are decades old.
The amount of “we have garbage collection at home” from the C and C++ communities during the rise of Java is a big part of my hatred of C++. That and watching classmates spin out in C++ classes in college.
Re:Advancing Memory Safety
by germandiago on Wednesday October 16, 2024 @07:08AM
(#41857740)
There is RAII and it works well most of the time.
Saying C/C++ denotes your poor understanding of C and C++, which are usually quite different in style and with very different safety characteristics regarding to code written in good style.
We just need to admit that we suck at it.