3 ms·

They said the ecosystem has backwards compatibility issues, not JavaScript.

• meiraleal 2y ago
  They are wrong. NPM is the biggest open source repository ever created, if you judge it by the longtail it will obviously be bad. There are plenty of projects there that exists for 15+ years and have great backwards compatibility, like jquery. Also, browser tech was changing very fast 10 years ago. Now it is quite slow and the JS ecosystem is consolidating the usage of modern features like ES modules, importmaps, web components.
  • esskay 2y ago
    NPM is hands down the worst package management system of modern times. I can't count the number of times we've inherited projects only to find half the packages are gone, broken or riddled with so many holes that they arent viable to continue using. The build and abandon mentality of JS development as a whole, combined with what is an extremely immature and convoluted package management system is half the problem with modern frontend development. You don't even have to go far for a comparison. Take a look at composer for PHP. It turned the language around and helped foster a very strong and stable ecosystem. NPM being the "Biggest" isn't something to be proud of. It's something to question - why is it the biggest? Is it because theres so many fantasticly useful packages? Or is it because everyone insists on reinventing the wheel or creating what are frankly idiotic packages that should neve have been created in the first place (left-pad anyone?).
    • crabmusket 2y ago
      It's the biggest because the web is the world's best deployment target, and JS is its native language. This leads to a massive number of developers of all abilities writing code and packages for it.