Now with Java and .NET upcoming adoption of ahead of time compilation to native code in the next versions.
Additionally with other languages like D, Rust, Go, Swift, Ada, Haskell, OCaml fighting for a place at the Sun.
There will be lots of options for those looking into languages with support for ahead-of-time compilation to native code in their reference implementations.
Thus pushing C++ deeper into the OS realm, while at the same time giving to those people other options to look for.
Hence my remark.
[0] There were other options, but they were largely ignored by the mainstream.
Funny that you list Ada and then ignore it offers the same features for systems programming as C++.
"Worse is Better" is Worse in the long run, I guess.
But even just considering new projects, I'd expect that C++'s inertia in terms of reputation, ecosystem and people's skillset/experience means that C++17 or even later will have plenty of time to measure up against the competition.
You are right, though.
C++ will continue to be used, much like Cobol has continued to be used for an eternity.
I've got coworkers who's first job in the programming business was Cobol maintenance. Old programmers from the 1960s are retiring in their 80s, and they need maintainers to write new code for various ancient mainframe systems.
Do remember, IBM is still selling System/360 systems today. http://en.wikipedia.org/wiki/IBM_System_z
These systems are running Cobol code from the 1960s, and they need to be updated to include XML, REST and all the other latest developments of development.
http://www.itworldcanada.com/article/the-future-of-cobol-why...
Similarly, C++ programmers are probably going to have an even _larger_ legacy than Cobol.
Cobol is very much alive today.
In fact by some measurements, Cobol is still more popular than Java and Javascript.
http://www.computerworld.com/article/2502430/data-center/cob...
[1] from my short readings, it's suited for simple table processing.
Weird, IBM has been trying to replace bare COBOL with higher level languages for years.
Probably not even "years", and closer to "decades" at this point.The point is that many of us, go to C++ because it is one of the few languages with ahead-of-time compilers available across multiple systems.
Now that we are experiencing a going native wave in terms of compiler toolchains for other programming languages, that reason is slowly becoming less relevant.
So many might choose another language, instead of waiting a few more years for the support to appear.
> And what is "C++ triad"?
gcc, clang and Visual C++.
HN posts about C and C++ tend to forget there are many more C and C++ compilers out there.
There are lots of compilers and OS out there besides those.
Which are what get discussed here most of the time.
http://en.wikipedia.org/wiki/Oracle_Solaris_Studio
http://en.wikipedia.org/wiki/HP_aC%2B%2B
http://en.wikipedia.org/wiki/IBM_XL_C%2B%2B
Notably, each of those can target an OS and hardware architecture made by the same vendor (Sun Solaris/SPARC, HP UX/PA-RISC, IBM AIX/POWER).