All projects in C++ will remain C++ forever.

Some projects will be coded in other languages, and stay in those languages. Wherever that language fizzles, the project will too.

> All projects in C++ will remain C++ forever.

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!

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.

I write software. In C++. Roughly 610,000 lines of C++. It's just fine, thank you very much.

That's pretty silly, lots of c++ projects have changed languages over the years. We get that you like c++ but let's not be myopic.

It's not silly at all, you're just not aware of the larger context the parent is speaking of (ironic considering accusations about myopia).

For example, the current c++ project I work on (for a large company) has over 1.5 million lines of c++, spanning over 5,000 files, with business knowledge and bug fixes spanning over 30 years.

It's not going to get rewritten in anything else, and the same goes for large amounts of other business software.

Depending on what that business software is doing I wouldn't be surprised in a few hundred thousand lines were written in something else. Microsoft (https://medium.com/@tinocaer/how-microsoft-is-adopting-rust-...), etc, are all doing this right now. But yea if you are writing low velocity, non mission critical software, no need to bother. On the other hand, there may come a point in time where that c++ project gets a boost by factoring the critical parts out of it into a safe language...

The one I’m working on is a behemoth and already has several hundred thousand lines of other languages (python, Java, scala) as part of it.

The c++ will be staying c++.

I don’t say this out of any affinity for c++(check my other comments for details), rather because for business reasons, the core of this system will always be c++.

In fact we a currently embarking on a multi-million dollar project to upgrade the application to run in the cloud and one of our biggest challenges is finding qualified c++ candidates.

Despite that, due to the complexity and scope of the application and years of business knowledge captured in obscure parts of the code, there is no consideration for it to be rewritten in anything else.

P.S. the software is absolutely mission critical (responsible for a non-trivial % of total company profit), hence the reason it's not going to get rewritten without a very, very compelling business case.

Three sentences, each with the same thing stated twice - three tautologies.

I.e., you did not understand it.