4 ms·
It's not that the package manager fixes the problem, it's that having 1 or maybe 2 or 3 canonical or popular package managers gets the implementer to fix the pr
by DubiousPusher 6y ago
It's not that the package manager fixes the problem, it's that having 1 or maybe 2 or 3 canonical or popular package managers gets the implementer to fix the problem.
The implementer, who has extensive knowledge of their own build system runs that aspect and creates a package that conforms to a universally expected output.
It's an incredible difference going from C++, where you end up in the details of all kinds of repos and build systems, to something like C# with Nuget packages where it's a simple command or single click to start using someone else's code.
- scoutt 6y agoConsider that C/C++, being highly portable, has support for many platforms and architectures, including the possibility of cross-compiling. I guess if a package manages works on all those architectures and platforms, then the implementer would have to support all of them, and it's not always the main objective. Let alone if there are several package managers.
- DubiousPusher 6y ago> guess if a package manages works on all those architectures and platforms, then the implementer would have to support all of them, Other "highly portable" languages handle this by simply having the developer include a manifest of the platforms their library works for. The package manager only shows compatible packages for the targeted platform.