3 ms·

I think you raise a good point, but when has this been the package manager's concern? When I type in 'dnf search' or 'apt-get install' or 'pip search' or the e

by niftich 10y ago

I think you raise a good point, but when has this been the package manager's concern? When I type in 'dnf search' or 'apt-get install' or 'pip search' or the equivalent, I don't get details, I just get a list of packages, one of whose title or description fields match what I pass on the command-line. A package's exported API is important (obviously, since without it you can't use it), but I'm not entirely sure the package manager is the best place to surface this information. Or maybe it should be, but no package manager so far does this well?

ianstormtaylor 10y ago
Yup, I don't think any package manager has ever really done this well. But what makes the problem worse is that npm advocates using lots of small modules, and using them in an environment (the browser) where duplication weight has big negative consequences. I think there's a real opportunity to unseat npm if someone applied to same kind of UX-first thinking to package management that has been applied to other areas.