3 ms·
C++ would have died except for three things, Java, the JRA and the web/Javascript. Java is a partial replacement for C++ that isn't quite good enough for desk
by Gibbon1 9y ago
C++ would have died except for three things, Java, the JRA and the web/Javascript.
Java is a partial replacement for C++ that isn't quite good enough for desk top applications. Hence C++ is still alive in that space.
The JRE was a anvil that language grabbed a hold of, which set them back about 10 years. because every language that depends on the JRE also suffers it's limitations.
And the web diverted resources away from native programming for 20 years.
However in the last 5-10 years we've seen a couple of well designed native compiled languages being developed. And those are going to replace C++.
And LLVM project and work done on KIT compilers provides a strong alternative to the JRE for language development.
Seriously, go is better than C++ now. And Rust is very rapidly getting there.
- pjmlp 9y agoWhen Java came into the scene, it was still a bit of a pain to write portable C++ code with the compilers catching up with the ongoing standard and indeed Java was a bit of fresh air in that regard. However, C++ was going strong in all relevant desktop environments, OS/2, Windows and Mac OS. Even on commercial UNIX systems everyone was jumping into CORBA as the next big thing, and I surely wouldn't ever bothered to touch CORBA with plain C stubs. Java had a lost opportunity with Sun being religiously against AOT compilation, an option only available via commercial JDKs, mostly for embedded deployment. Graal and SubstrateVM are changing that, but it will still take a couple of years to actually change everything. Project Metropolis calls the Java on Java plan, the next 20 years. Not only are those web browsers written in C++, throughout those 20 years C++ has been present on web pages via plugins and now WebAssembly. We cannot have LLVM and kill C++ as well, unless you are planning to rewrite into something else. Go is a better C, but definitely not something worthwhile against C++. Using Git urls as package names and writing generic code as if using Borland C++ 2.0 for MS-DOS with BIDS pre-processor macros is definitely not something enjoyable. Rust is improving at a good pace, but until it cuts its dependency on LLVM it will always depend on C++ tooling. Love the language, but suggesting that it is at the same tooling level as C++ to business using it for the last 20 years is just irresponsible. There are lots of domains, even on embedded where Rust eco-system just isn't there nor does it seamlessly integrate with existing workflows. Using a programming language is much more than just installing a command line compiler and hacking away on a text editor. It took C++ almost 20 year to replace C in many high performance domains, and for better or worse, it is mostly copy-paste compatible with C89. Any language that wants its place needs to account for similar uphill battle in all domains.