This may be similar to Java vs Kotlin race, where Kotlin added improvements, while Java was still stuck in 1.8. The answer was to add as many features to the language as possible. Looks a bit like C++ is starting to do the same.
This may be similar to Java vs Kotlin race, where Kotlin added improvements, while Java was still stuck in 1.8. The answer was to add as many features to the language as possible. Looks a bit like C++ is starting to do the same.
Because Java is losing market to languages with many features. Which is good. Given history of Java under Oracle supervision, and the availability of Rust, Go and C#, I won't ever touch any JRE-based language.
Rust is much less common than version control, but so is C++.
This was a thing in the early 2000s, but very certainly hasn't been the norm for a very long time now, at least in my part of the world.
If it's different where you are, you need to take immediate action and inform your company leadership of this extreme liability.
Some of the craziest things about C++ metastasised and are now everywhere in programming, so they don't seem as crazy - but if you're a non-programmer they will still be crazy in C++ and Rust doesn't have them.
For example why does "const" mean immutable? In Rust it means constant, like you'd expect. Why is "Hello" six units of storage space? In Rust it's five, because duh. Why does passing this HugeDoodad into a function expensively copy the HugeDoodad? In Rust it doesn't do that.
This is an exaggeration.
For me, C+11/C++14 made the language much more approachable and readable.
It was only that from then on, the language was to be updated regularly.
There are, surprisingly, quite a few, including some very high-profile ones.