Comment by gurkendoktor
7 years ago
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.
> 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.
Having a single master, instead of having to please every compiler vendor, helps.
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.