These posts have been around ever since I started to learn how to program. When I was a wee little lad, everyone told me that C++ was going the way of the dinosaur and no one would ever need to learn it.
That was 10 years ago. It still hasn't happened. Meanwhile, blog post after blog post is written about how C++ is dying when it simply isn't. Maybe it will happen sometime in the future, but as of yet no language solves the same problems that C++ does. Not D, not Rust, not Go. Every single one of these arguments is colored by the specific problems the author has spent their life solving. If none of those problems benefit from C++, then they will inevitably come to the conclusion that C++ is useless, and then yet another "C++ is dying" or "C++ considered harmful" blogpost is written. Meanwhile, reality doesn't care.
True. What reality cares is that the programs run where they need to run and it's "portable"
And as much as I would want all programs to run on Linux/Mac OS only and not care about a user interface, there are still programs that need to do that.
Do a cross platform desktop software that runs in Windows/Linux/MacOS. I know three possible answers: Python, Java and C++. Mono maybe a choice as well, but it requires installing Mono.
Now, how to do a software that runs on an embedded linux device.
That was 10 years ago. It still hasn't happened. Meanwhile, blog post after blog post is written about how C++ is dying when it simply isn't. Maybe it will happen sometime in the future, but as of yet no language solves the same problems that C++ does. Not D, not Rust, not Go. Every single one of these arguments is colored by the specific problems the author has spent their life solving. If none of those problems benefit from C++, then they will inevitably come to the conclusion that C++ is useless, and then yet another "C++ is dying" or "C++ considered harmful" blogpost is written. Meanwhile, reality doesn't care.