2 ms·
As someone who has used jQuery on one project for about 10 years I disagree. Some big problems: 1. Upgrading jQuery has been hell over the years. Literally eve
by setquk 8y ago
As someone who has used jQuery on one project for about 10 years I disagree. Some big problems:
1. Upgrading jQuery has been hell over the years. Literally every time something wierd breaks. Major version like the 2.0 transition meant major rewrites.
2. Most of the plugins seem to of varying quality between dire and just about usable but even the best we used died and got abandoned. I've had to fork, maintain and fix a load and then most of the contributors of those plugins don't know or care about updates or forks or pull requests or are total assholes so we're doomed to maintain them forever.
4. It is terribly slow in some circumstances. You don't know this until you find some client who is using a Citrix terminal deployment and is forced to use some tail end supported version of IE. And they are the loudest complainers.
5. It's pretty difficult to get rid of it. The tentacles are right in there. That monkey is on your back forever.
6. It's huge. Core isn't but by the time you've dragged in everything in via plugins to be productive you've got a meg of insecure god knows what crap running on your front end.
Regardless of the progress in browser tech, having your stuff run like ass, which it will in the future (I know after 10 years), because it's easy and convenient is just wrong.