News for hackers. Stuff that matters.
Re:What should go into the C++ standard library (2018) by htfy96 on Wednesday February 27, 2019 @09:54PM (#19268659)
The problem is that the community has already diverted in the way to organize sources, and each of them believes they have the best solution. Similarly, all C++ issues originate from the fragmentation of community: some (maybe 2/3) prefer include a network lib because it facilitates their daily development, while others (maybe 1/3) may have different ideas because they don't use it/they need performance over usability/they want to use this on embedded systems/their own stdlib fork doesn't want to support it. Meanwhile the committee cannot enforce everyone in the community to do something because it has no real-world control on either compiler dev/user community.
Re:What should go into the C++ standard library (2018) by epage on Wednesday February 27, 2019 @11:26PM (#19268944)
The concern over fragmentation is why believe conan's approach is the best: decouple dependency management from build rather than forcing everyon to align on build.

Still has its hurdles but it is a step in the right direction for trying to wrangle the wild west of C++.