DEV Community

Discussion on: Is jquery dead?

Collapse
jasongabler profile image
Jason Gabler

Funny you should ask. I just had to work with some customers of a customer who are in China. All sorts of problems come into play when you're dealing with JavaScript and CSS libraries, CDNs and The Great Firewall. It turns out, one of the issues was an occasional inability to access jQuery and dependent libraries. I could've opted to just have all libraries local, but it was a small set of work. So, I decided to nix jQuery and rewrite all of the bits in native JS (we're not at Bootstrap 5 yet.). First, it had been quite some time since I wrote much of anything that wasn't dependent upon jQuery. As a full stack developer, I have to pick and choose how I spend my time staying on top of things and it often comes down to something intersecting with "if it ain't broke, don't fix it." For quite some time jQuery was working fine for us. But now, it was at the heart of a problem and this caused me to brush up on the latest offerings of native JS. I must say, things have greatly matured. JavaScript's interaction with the browser, particularly events and the DOM, has lost a lot of its earlier, convoluted feel. Code ends up more succinct without being unduly terse, making much more obvious sense when browsing through it. I also found I was doing a lot less back-and-forth with the documentation (meaning it felt more natural to code with it) and coding with calls, parameters and tag attributes was much less tedious and error prone. This sounds much of what I was looking for when I went to jQuery so many years ago. So, if JavaScript has more than a certain threshold of solving the problems of why we went to jQuery in the first place, there's really no reason to force our customers to download and execute yet another layer of code in their browsers. So, yes.