3 ms·
jQuery’s API is still (and, probably, forever will be) miles ahead of the native DOM API. Cross browser compatibility was just one of the reasons the world fel
by tambourine_man 6y ago
jQuery’s API is still (and, probably, forever will be) miles ahead of the native DOM API.
Cross browser compatibility was just one of the reasons the world fell in love with jQuery.
- michaelpb 6y agoPersonally, I find it miles behind the modern native DOM API, which is what I prefer now, but I guess to each their own! (And I'm not even against jQuery, I used it extensively mid-2000s-2010s, including on fairly large SPAs, and even taught a class with it for a little under 2 years, but again, to each their own)
- tambourine_man 6y agoIt's a lot more verbose and less powerful. I mean, the http://youmightnotneedjquery.com http://youmightnotneedjquery.com site reads like a parody even in 2021.
- michaelpb 6y agoI guess it truly does come down to preference and perception, as looking over that link you provided I actually had the opposite reaction! I prefer the DOM API in each example, save for examples that are clearly out of date to support old versions of IE without a polyfill (e.g. all the AJAX examples at the top can use fetch, other can use Object.assign, no use of the iterator interface anywhere, etc)
- tambourine_man 6y agoThis is something I really can't fathom. It takes twice as much typing without the chainable, unix pipe like API. I really don't get it, but I've been baffled by this industry's decision for more than a decade.