3 ms·
There are a fair number of answers about it being old, and I think that it's really important to contemplate what age means for software: the most obvious answe
by acdha 4y ago
There are a fair number of answers about it being old, and I think that it's really important to contemplate what age means for software: the most obvious answer is that you can now use newer standard APIs for a lot of what jQuery did (which, to be clear, is great!) but also that there's been a lot of time to build a ton of projects using jQuery and for those projects to follow the common trajectory of starting simple and growing more complex over time.
Programmers tend to love building new things more than maintaining code and we're _really_ prone to misattributing the causes of problems, especially when that would mean admitting that we're not as good at managing complexity as we hoped. When Facebook's marketing push really got rolling, it started a fad of people crapping on jQuery and talking about how amazing React was — and I saw almost none of them built something which was either faster or, within 6 months, much easier to work on. The only exception I remember was a time where the React rewrite was what gave them political cover to slow feature development enough that they could fix a known design flaw.
That's not to say that newer tools are bad but the teams who did see benefits were already relatively mature: they actually measured performance, had a stable testing approach, refactored regularly rather than letting technical debt pile up until is burst into flame, etc. They would have been successful with almost any tool, and tended not to trash-talk jQuery when they left it behind since part of experience is understanding how much your choices matter.