3 ms·
It seems a bit weird to criticise lots of people for trying to solve the dependency problem. I know lots of people hold up npm as the standard. Npm came out aro
by jimnotgym 5y ago
It seems a bit weird to criticise lots of people for trying to solve the dependency problem. I know lots of people hold up npm as the standard. Npm came out around 10 years ago, Node around 12. Both of which had the benefit of hindsight at how the problem had developed for other languages. Python came out 30 years ago and pip came out 20 years later. Of course there is a lot of stuff left behind. What do people suggest, a breaking change, maybe? Python 4?
- m4rtink 5y agoI'm not sure NPM is a good example of anything, with its insane dependency chains and the barrage of security issues.
- georgyo 5y agoNpm is absolute hell. One thing that people do like about JavaScript is that you can import multiple versions of the same package. This solves that depA requires 1.0 and depB requires 2.0. However this makes auditing nearly impossible. Small projects can end up with well over a thousand dependencies that is just unmanageable.
- selfhoster11 5y agoNPM is the perfect example of overly-atomised dependencies. No project should have a dependency graph numbering in the hundreds or thousands of nodes. IMO, the Java or APT packaging ecosystems solve the issue in a far superior way.