News for hackers. Stuff that matters.
Re:What should go into the C++ standard library (2018) by ryandrake on Wednesday February 27, 2019 @10:14PM (#19268736)
Please, no.

We don’t need yet another package manager. Every language seems to have to have its own package manager, separate from my operating system’s package manager, that does exactly the same thing but in an incompatible way.

Now, if I want to know what software I have on my system, I need to use five different list commands instead of just one. If C++ had its own package manager, that would mean six. Please help to stop this madness, not perpetuate it.

Re:What should go into the C++ standard library (2018) by jeffdavis on Wednesday February 27, 2019 @10:34PM (#19268791)
It's not madness; each approach has problems.

In particular, distros generally work best when one version is enough, or maybe a few versions. Anything else leads to dependency hell.

Re:What should go into the C++ standard library (2018) by erik_seaberg on Wednesday February 27, 2019 @11:38PM (#19268985)
Dependency hell comes from binaries that insist on not using the shared library provided by the distro through the package manager. Windows suffered from not having a package manager in the dark ages, leaving installers to silently clobber each others' changes.