Projects coded in Rust will remain in Rust, too. Projects coded in Go will remain Go. Projects in Java will remain Java.
So, the advice above is just to avoid all languages (which, by the evidence, he does, seeming to know nothing meaningful about any).
There is an exception, though. Projects in C have frequently transitioned to C++, often with great success, notably Gcc and Gdb.
People language hop all the time. I 've seen people rewrite apis from python to Go, java to go, python to scala, Go to rust, etc etc etc.
Re:Embracing Modern C++ Safely, Book Review
by PaulDavisThe1st on Monday May 30, 2022 @11:24PM
(#31565814)
I write software. In C++. Roughly 610,000 lines of C++. It's just fine, thank you very much.
Anybody who believes this ought to think it an excellent reason to stay away from C++. For actual software projects I mean. Obviously if you want a career writing books (like the one reviewed) or on the conference circuit, or training, or several other prospects, this is great news. C++ is a good language it which to charge somebody $1000 per day plus expenses to tell them what they already knew.
But if you actually write software, or worse, if you need software but that isn't really what you actually wanted to do just a necessity like farmers need to know how to drive a tractor, then this ought to put you off. C++ doesn't want to be your best choice, according to ncmncm anyway, it wants to be a trap you fall into and can't get out of. Run away!