All good things must come to an end – Museum calling for jQuery?
Recently, I came across an old discussion on the pros and cons of using jQuery and its future. The discussion had taken place back in 2016 with experts like Jen Looper, Todd Motto, and Jeremy Likness agreeing on the fact that “Angular, Knockout, React, etc. have all contributed to diminishing the need for jQuery.”
The discussion itself as well as the title of the post “Is jQuery Still Relevant?” got me thinking. Is this really happening? Is jQuery becoming redundant, for real?
After a bit of research, I found some other posts and discussions all focusing on whether jQuery is still relevant or not and if you would be better off moving away from the library.
And then… BOOM! GitHub announced that they are removing jQuery from GitHub.com frontend.
We’re finally finished removing jQuery from https://t.co/r2QL2aHBfa frontend. What did we replace it with? No framework whatsoever:
• fetch for ajax,
• delegated-events for event handling,
• polyfills for standard DOM stuff,
• CustomElements on the rise.
— Mislav Marohnić (@mislav) July 25, 2018
The team wrote in a recent blog post:
We have recently completed a milestone where we were able to drop jQuery as a dependency of the frontend code for GitHub.com. This marks the end of a gradual, years-long transition of increasingly decoupling from jQuery until we were able to completely remove the library.
Let’s take a closer look at the reasoning various sides offer on the relevance (or irrelevance) of jQuery.
How it all started
The original and most prominent feature that made jQuary a God in web development was the cross-browser compatibility that, back in the day, was still a huge issue.
Midway, jQuery added tons of extra functions and wrappers like.ajax(), .post(), event binding helpers that made it super amazing for web developers but it also made it tricky for frontend developers since, at some point, they would find it quite difficult to know what was actually going on behind the curtains.
What’s more, new tools that came along the way, like Angular or React, took away a big chunk of the spotlight.
There was another factor contributing to jQuery’s downfall and that was the team’s rather sluggish updates and releases. The last couple of years or so the team has moved to a new system with roughly two releases per year. Not to mention that these releases focus on removing features rather than adding new ones or making groundbreaking changes.
Moving to some real-time examples, even before the news bomb from GitHub dropped, there were various companies documenting their decoupling from jQuery and how they ended up with a faster platform because of that.
On the other hand, if you take a look at jQuery usage statistics you cannot really see the numbers going down. What I gathered from the discussion on the Telerik blog I mentioned earlier is that most of this usage is legacy rather than new applications.
There is always the other side of the coin
The trend of moving away from jQuery can be documented as early as 2014 (if my research is correct). But there are some developers that still keep the jQuery flag high.
Some others may recognize the withering trend of the library but strongly believe that we have not yet seen a definite downfall.
jQuery isn’t going to go anywhere until businesses can realistically assume that the vast majority of their customers are on modern browsers. So it might be dying, but, much like Adobe Flash, it’s going to be a slow death.
There may be hope yet
The jQuery team has mentioned in 2017 that they are working for some big things for the 4.0 release.
Indeed, the roadmap shows some interesting ideas the team has been working on like create a web download builder and add automated code coverage. Will this be enough for the legendary library to gain back all the lost momentum?
We will see. For now, you can let us know in the poll below if jQuery is still an important tool for you.