News for hackers. Stuff that matters.
Re:Why the C++ standard ships every three years by gurkendoktor on Sunday July 14, 2019 @01:25AM (#20431809)
Swift had the same ABI issues as C++, but when most packages ship as source code, it's not that big of an problem. This is precisely the thing that a standardized package manager can establish.

I think it's a bit of a catch-22. C++ projects are so rare and monolithic that reinventing the wheel every now and then. But maybe more (smaller) projects would happen in C++ if there were polished libraries for reasonably common requirements like sending a SOAP request.

Re:Why the C++ standard ships every three years by gumby on Sunday July 14, 2019 @09:31AM (#20433257)
> Swift had the same ABI issues as C++, but when most packages ship as source code, it's not that big of an problem

... and when there's essentially a single build system for Swift code. While for C++ there are several.

Re:Why the C++ standard ships every three years by pjmlp on Monday July 15, 2019 @12:06PM (#20442111)
Having a single master, instead of having to please every compiler vendor, helps.
Re:Why the C++ standard ships every three years by gurkendoktor on Sunday July 14, 2019 @12:07PM (#20434165)
Over-edited my comment, should have been:

> C++ projects are so rare and monolithic that reinventing the wheel every now and then...

...does not hurt much.