Every project must colonize a valley of the language, declare a dialect, and bit-fiddle their own thing.
It might be a measure of popularity, but not of unity.
Lambdas are nice to have, just don’t nest them more than once.
I kinda wish things like std::variant had shorter syntax.
if anything i’m not a fan of c++ introducing language features as long verbose functions than to confidently make it an operator or a keyword.
However it would be imperative for a push such as Carbon[1] to be similar to the kotlin to Java. A modernisation that simplifies , maintains backwards/forwards compatibility and reuses established libraries and tooling.
This however will need a entity that can champion and push it forward with a strong enough project to anchor it in the mainstream.The transitions are doable ,like Android dev from plain java to kotlin , or in OSX moving from Objective-C to Swift.
Additionally borrowing a robust batteries type standard library to reduce the sprawl of coding options and funnel greenfield projects into best practices and less boilerplate.
[1] https://www.infoworld.com/article/2337225/beyond-c-the-promi...
- The current CPP version is extremely bloated
- CPP is not going away anytime soon
- The rise of Rust/Go/Zig is not fighting for CPP's seat
- You can target CPP code using any of these aforementioned languages
- Rust has never claimed to be "safer", it just makes it harder to write unsafe code
Until current computers cycle out, people will largely keep their 1-3 year old machine with sane amounts of memory. If we start seeing large numbers of machines in the wild with 4GB of memory, then maybe software will adapt. But that won't be for several years yet.
Projecting into the future, hardware expenses have always been dwarfed by salaries. I don't expect that will change enough for it to be noticeable.