3 ms·

There isn't a benefit to OSS projects all competing for the same audience and bloated feature set. Picking a subset, being opinionated about it and the implemen

There isn't a benefit to OSS projects all competing for the same audience and bloated feature set. Picking a subset, being opinionated about it and the implementation isn't wrong. For developers, there is such a thing as picking the right tool for the job, even if it isn't your favourite one you usually use.

mcfedr 5y ago
As much as people moan about npm community, it does give you many choices and you can avoid complicated massive libs
- Ygg2 5y ago
  ...By adding thousands of libs, turning node_modules into a multi GB folder. Oh, and each of which can be compromised by an unscrupulous actor. Good luck auditing that.
  - p2t2p 5y ago
    Like if any other thing with automatic package management is any better. .m2/repository is 5 gb on my machine. Rust crates? Go packages that are neatly tucked away too? Node just makes it visible and in your face by putting the node_modules in you project directory. Besides, what’s the alternative? Write stuff yourself? Put stuff in language stdlib? Even minimal service requires _a lot_ of things to do minimal stuff.