Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Charon92835410dThese other frameworks generally provide more utility than DOM manipulation.
My gripe with jQuery is because it does things that native JS now does in a *slightly* prettier manner while abstracting away everything it's actually doing.
Fast-Nop1512710djQuery is obsolete for several reasons:
1) Modern vanilla JS can usually do its job for simple cases with direct DOM manipulation.
2) Simple animations are available via CSS transitions which the browser can schedule in parallel by itself, and complex animations usually don't belong on a production website.
3) For complex things, you don't even want direct DOM manipulation because that ends up in a mess. That's what frameworks address.
4) Why incur another dependency if it isn't necessary?
5) It's usually another file that is downloaded, and while http/2 makes that less of a problem, it's still one additional round trip. Especially on mobile, you don't want useless roundtrips.
The only reason for jQuery today is if you have legacy jQuery plugins and nobody would pay for a rewrite.
I've got a widget of medium complexity on my site, and it was written 10 years ago. Took me two days to convert that into vanilla JS.
beegC0de136410djQuery is likely slower than just using the native JS due to overhead of abstracting calls to DOM functions. But the DOM functions themselves nowadays are easy to use without abstraction.
devTea230069dMost modern library only do one thing each unlike jQuery that do everything with the annoying $ syntax
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job