Re:Removing jQuery from GitHub.com frontend
by Macha on Wednesday July 25, 2018 @07:11PM
(#17613780)
I mean, when you think about how many people were using jQuery for
(a) cross-browser compatibility, which mostly works now (except for cutting edge stuff, which is pretty optional) (b) $.ajax (uses that could be replaced by window.fetch) (c) Sizzle (Replaced by document.querySelector[All])
Re:Removing jQuery from GitHub.com frontend
by Piskvorrr on Thursday July 26, 2018 @05:02AM
(#17616065)
Yeah. And IIRC, all of this came about as "let's take these awesome pieces of jQuery (which were written because browsers sucked) and reimplement them natively." Now the roles are apparently reversed, with jQuery being the Big Bad?
Re:Removing jQuery from GitHub.com frontend
by floatboth on Wednesday July 25, 2018 @07:58PM
(#17614020)
(d) the plugin system, which is replaced by Custom Elements (but unfortunately the React crowd is there with their own custom private component system)
Very much this. There are very few scenarios in which I’d recommend jQuery nowadays, but I still have mad respect for the project itself, for its legacy, and for the positive impact it’s had on front-end programming.
I think it's impressive that even when I'm not using jQuery (haven't in many years), I find myself writing code using features/capabilities where jQuery was an obvious inspiration.