News for hackers. Stuff that matters.

A comment on C++26 Reflections adventures and compile time UML. Parent comment

Re:C++26 Reflections adventures and compile time UML by corysama on Sunday August 03, 2025 @01:33AM (#44774291)
The history of C++ has been one long loop of:

1. So many necessary common practices of C++ are far too complicated!

2. Std committee adds features to make those practices simpler.

3. C++ keeps adding features. It’s too big. They should cut out the old stuff!

4. The std committee points at the decade-long Python 3 fiasco.

5. Repeat.

[ Parent | on HN ]
Re:C++26 Reflections adventures and compile time UML by birn559 on Sunday August 03, 2025 @01:46AM (#44774353)
Do they point at python 3? They were committed to backward compatibility long before python3 happened.

To me it feels like they have fleshed out key paradigms so that is not a mess anymore. They are not there yet with compile time evaluation (constexpr consteval,...), at least with C++20, not sure if it's mostly finished with C++23/26.

The language itself and std is quite bloated but writing modern C++ isn't that complicated anymore in my experience.

[ Parent | on HN ]
Re:C++26 Reflections adventures and compile time UML by zozbot234 on Sunday August 03, 2025 @06:12AM (#44775497)
It's pure Stockholm syndome. There's even a nice C++ committee paper that summarizes this as "Remember the Vasa!" https://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p0977r0...
[ Parent | on HN ]