5 ms·

That comes at a cost of lots of volunteer hours. I’m not sure if it would scale to NPM’s massive size.

• naniwaduni 7y ago
  npm's size is not independent of its curation strategy. This can be construed as a good or a bad thing.
  • kjksf 7y ago
    NPM's size is first and foremost dependent on the popularity of JavaScript. All other "modern" (where "modern" is "last 20 years") package managers have zero curation. Perl, Python, Ruby, Go, Rust, Dart, JavaScript. You say: "if they had curation, they would be better". I say: "if they had curation, they would have lost to a competitor that doesn't have curation". People care about having more packages much more than abstract fears of security or quality of those packages.
    • umanwizard 7y ago
      > modern Apt is about 20 years old, and the most famous apt package repos (I.e., the Ubuntu project) is much younger than that.
    • TeMPOraL 7y ago
      People care about having more packages much more than abstract fears of security or quality of those packages. At their own peril.
    • justinclift 7y ago
      > People care about having more packages much more than abstract fears of security or quality of those packages. You're partially right. Some people haven't yet learned (eg the hard way, or whatever) that quality does matter. Hopefully most of those people will learn to appreciate and demand quality over time, instead of the current anything-goes-approach. In the meantime, things like this npm package example will continue to give npm/javascript black eyes (repeatedly) and help make that happen. :)