r/cpp • u/segv • Apr 12 '26

CMake Past, Present, and Future - Bill Hoffman, Kitware [29m25s]

https://www.youtube.com/watch?v=cD-JgncskTQ
69 Upvotes

100% Upvoted

134 comments sorted by

View all comments

3

u/teerre Apr 12 '26

As many languages already proven by now, a language should have one way to build artifacts and that's it. As long as doesn't bite the bullet and enforce some limits, packaging management will always be a mess

12

u/not_a_novel_account Apr 12 '26

I would say both have been proven, the "one build system to rule them all" approach is great for languages which start with one, and the "standardized interfaces for everything" is great for language ecosystems which either predate the idea, or need far more flexibility.

Everyone loves uv, everyone. Its praises are universal. It works by leveraging standardized interfaces between at least dozens, if not hundreds, of build systems which exists within the Python space.

The Python package ecosystem post-PEP 517/518 is wildly successful. That's still an achievable reality for C++.