4 ms·
In a way, it's an end of an era. What jQuery did for the industry when it first came out was amazing. Normalizing differing browser APIs, making cumbersome APIs
by brianshaler 10y ago
In a way, it's an end of an era. What jQuery did for the industry when it first came out was amazing. Normalizing differing browser APIs, making cumbersome APIs more palatable, providing powerfully expressive query selectors, enabling fairly trivial plugin development, and the nifty monadic chaining.
Some of those issues have been addressed by browsers, making vanilla JS a little less unreasonable. For other bits, rails-ujs provides some niceties that aren't worth carrying all of jQuery to have. These days most developers will want to use le framework du jour, and don't need jQuery for DOM querying and manipulation.
- swalsh 10y agoLet's be honest, jQuery was a patch for the IE6 bug.
- crdoconnor 10y agoIt was primarily a saner query language for the DOM.
- xutopia 10y agoIt was much more than that. jQuery made difficult things easy and paved the way for future technologies by using browser specific abilities and providing a unified API for developers to use. It also standardized around a plugin architecture making it easy for people to write code others could easily reuse. If you think there is only one iE6 bug that jQuery helped alleviate you'd be wrong. There are thousands of quirks/bugs/proprietary crap that jQuery handled for web developers. Reducing it to an IE6 bug fix is out of touch with reality.
- igravious 10y agoThey meant, the bug that was IE6 (all of it).