3 ms·
A combination of: [ ] Will probably be abandoned in less than a year [ ] If it does not get abandoned, it will not follow semantic versioning and introduce br
by trinovantes 5y ago
A combination of:
[ ] Will probably be abandoned in less than a year
[ ] If it does not get abandoned, it will not follow semantic versioning and introduce breaking changes outside of major releases. A routine `npm upgrade` may or may not break everything
[ ] If it follows semantic versioning, there will probably be a major release with breaking changes every few months
[ ] Probably has a 500MB+ dependency tree
[ ] Frequently has security issues with a dependency 4 levels deep and you can't upgrade without conflict with another library or because a dependency 2 levels deep is abandoned
Do these issues exist in other languages? Sure but those incidents are quite rare and isolated. But these issues happen *way* too often in the JS ecosystem.
- mimixco 5y agoHow can the most popular language in the history of computing be abandoned in less than a year? There is more code right now running JS than there is in all other languages combined.
- trinovantes 5y agoI was referring to the majority of JS projects
- mimixco 5y agoI'm still not understanding. How would the majority of JS projects change? And why?
- mtberatwork 5y agoThey are talking about libraries being abandoned or otherwise introducing breaking changes.
- mimixco 5y agoAh. Thank you. That problem is caused by developers who choose to introduce breaking changes in new releases, or who don't fix known bugs. Those are common problems in a lot of software.
- dyingkneepad 5y agoThis! But also: [ ] Requires a Javascript interpreter, maybe even a full browser engine to run. May consume 2gb of RAM just to show me a screen.