3 ms·
Part of the problem is probably the high amount of churn. In the Javascript world this is absolutely ridiculous, people just can't seem to leave things alone an
by RedShift1 5y ago
Part of the problem is probably the high amount of churn. In the Javascript world this is absolutely ridiculous, people just can't seem to leave things alone and it causes a cascading effect, where one developer makes an API change and suddenly thousands of developers have to deal with a change that typically brings them no benefit. It's pretty much a self-inflicted wound.
- donatj 5y agoI don’t understand the sheer volume of major version increments in JS projects. Avoiding breaking changes should be one of your main goals as a developer, yet I swear some libraries have major version increments multiple times per month.
- kayodelycaon 5y agoModern JavaScript grew up in the culture of “move fast, break things”. Combined with JavaScript having a limited “vocabulary” and being the new PHP, you end up with a lot of churn as people start building large applications without the tooling for it.