3 ms·
"Benefiting from the largest ecosystem in the javascript space" is not a "contrived" reason, what the hell?
by scrollaway 4y ago
"Benefiting from the largest ecosystem in the javascript space" is not a "contrived" reason, what the hell?
- soulofmischief 4y agoContrived in that OP focused on particular developer needs and ignored the rest. > What most JS developers should really care about is the ecosystem, the tooling, the documentation, the code quality, and the testability of their chosen framework This isn't just OP's opinion. OP is lite gatekeeping by suggesting that most JS developers should share their opinion. I will agree that testability is paramount, but lacking specific contexts (embedded, high-perf, security, etc) the rest of the heuristic deals with a series of trade-offs. OP has possibly worked in a limited context when writing front-end code, and has not been forced to make trade-offs. The most glaring issue with their argument is that developers should stick with libraries that have large ecosystems and tooling. This is an anti-progress, anti-innovation sentiment which does not even hold up. Like another poster said, there was no reason to ever drop jQuery and move to view libraries if ecosystem and tooling were paramount.