3 ms·
There are a lot of package ecosystems, but more packages, and one of these packages will always depend on something implicit. Building a new system is not goin
by pastage 7y ago
There are a lot of package ecosystems, but more packages, and one of these packages will always depend on something implicit.
Building a new system is not going to help. Xkcd 927 about standards applies
- Uehreka 7y agoI agree that we shouldn’t try and wrangle npm, gems, cargo, etc. into one package manager. I have no problem with different communities having different package ecosystems. My main problem is that when it comes to C/C++ dependencies, the package ecosystem defaults to installing globally and has no standard way to specify dependencies aside from having instructions to “sudo apt install these 20 libs”.