3 ms·
I’m guessing that the problem is the search engine? It would be interesting to compare the search/suggestion engines of CPAN/PyPI/rubygems/npm/CRAN, because th
by CaliforniaKarl 9y ago
I’m guessing that the problem is the search engine? It would be interesting to compare the search/suggestion engines of CPAN/PyPI/rubygems/npm/CRAN, because this can’t be a problem that has only been faced by npm.
- tyingq 9y agoPart of it is scale and growth rate. CPAN has around 36k packages but it's been around decades. NPM exceeded 350k a while ago. See http://www.modulecounts.com http://www.modulecounts.com
- TAForObvReasons 9y agoNPM used to have its own search, then one day in late 2016 decided to outsource it to https://npms.io/ https://npms.io/ . That may be directly related to the issue at hand
- SenHeng 9y agoUsing the search terms used in TFA, npms.io seems to return the expected results compared to whatever's used on npmjs.com. So I don't think we should blame them.