Re:Why Rust Isn't Killing C++
by oxfordmale on Thursday May 02, 2024 @01:01PM
(#40238514)
Just go tell your CEO you are going to rewrite all the C++ at your company into Rust, taking months of Engineering effort, and deliver the exact same functionality at the end of it.
A refactor needs to be part of a strategic initiative. If security is paramount to an organisation, a refactor to Rust can be worth it. Doing new projects in Rust can also be a valid decision.
My company did rewrite some old code - starting about 15 years ago. It took a billion dollars over many years to get to more or less feature parity. (there are some rarely used features we will never port). On hindsight I think we should have refactored the existing code in place - it would have been similar costs and we are already seeing with hindsight many of the things we thought was good are not where we want to be with the new code either.
Reasonable people could disagree about whether or not a migration of a particular codebase is worth it. A general / absolute argument in either direction is not reasonable. And this whole thing is muddied by the fact that there’s CERTAINLY a material contingent of, frankly, incredibly delusional C/C++ developers that can’t stand the mere thought of change, nor the implication that these languages may not be perfect. Some even wearing the inscrutable nature of their tools of choice as a point of intellectual pride.