3 ms·

It's not a language problem. It's a cultural problem. Last I checked create-react-app pulls around 1k transitive dependencies. Can't really blame JS for that,

It's not a language problem. It's a cultural problem. Last I checked create-react-app pulls around 1k transitive dependencies. Can't really blame JS for that, can we?

ajdude 5y ago
This whole situation reminds me of that post a little while ago > I will pay you cash to delete your npm module https://news.ycombinator.com/item?id=29240952 https://news.ycombinator.com/item?id=29240952
- a3w 5y ago
  So finally F.L.O.S. Software pays out. Shame that the dev did not apply for some compensation. All in all, not very rational of him.
tomjen3 5y ago
Keeping dependencies loosely coupled and reusable has been best practice since forever, but it is only really with NPM that it has become the default.
- chrisandchris 5y ago
  But actually it's more like dependency hell because you pull in the same dependency in N versions and you can't update transitive dependencies in a senseful matter? And you get a lot of libraries that are like 4 lines and computing basic operations (like there was a lib "isOdd"... i mean x% 2 === 0?). So you won't gain anything from this type of dependency management, because it is way to complicate to understand and to manage for a developer.