For folks who still work with jQuery, for personal or professional projects, what is the overall context of this work? Do you expect this to be refactored at any point?
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (63)
I still use jQuery with WordPress, and I don't expect that I'll stop any time soon. Most of the time a Wordpress plugin will need to load jQuery anyway, and it's really nice for sprinkling JavaScript onto a static page. I write less code than I would with Vanilla JS, and it has animations & ajax built in. Sure, I could piece animations & ajax together another way, but I don't see the reason when jQuery has both.
I'm not a luddite: I use React when I build full-blown web applications. I've also used ES6 features to build apps with Vanilla JS before. But unless bundle size is a major constraint, I still feel perfectly happy reaching for jQuery in 2021.
I wrote about this more extensively in my article with the clickbait-y title, "Hating jQuery doesn't make you cool." Link below π
Hating jQuery doesn't make you cool
Tyler Smith γ» Jul 27 '20 γ» 3 min read
Have you looked at Alpine.js at all? I quite like that as a jQuery replacement because:
These days I don't really like including jQuery by default on new projects because a lot of it simply isn't needed, but at the same time doing a lot of that stuff in vanilla JS can be a chore. Alpine's so far proven to be a good solution for what I used to fall back to using jQuery for.
Alpine is absolutely amazing. It's become my favorite tool for adding interactivity on server-rendered apps that I build with frameworks like Laravel. And Alpine recently added an equivalent of jQuery's slideToggle(), which is the feature I needed most often from jQuery.
I'm not terribly concerned about the extra kilobytes I get from using jQuery. jQuery doesn't block the DOM from rendering, and it doesn't require activation bootstrapping the way that a framework would: it just needs to download and parse. It's very different than React where you can't render anything until the library is downloaded, parsed, and your app code executed. Even server-rendered React has issues with links not working until the app is fully hydrated.
Avoiding extra kilobytes is nice, but it's easy to go down a rabbit hole where we focus on reducing the kilobytes of JavaScript because it's easier to measure than other higher-impact UX like avoiding page jank, creating useful error states, avoiding responsive issues, etc. Alpine feels nicer to use in a lot of cases though!
In the same way I'm doing with Vue.js, drop in the script tag and swap out the JQuery. I'll check out Alpine, Vue I just seemed to "get it" quite quick.
Alpine has almost everything I like about Vue without the build the steps. It's one of the best front-end tools to come out in the past few years.
Yep with the cdn script there is no build for Vue either so fully with you on such a low impact way to improve
vuejs.org/v2/guide/installation.ht...
+1 for Alpine, I love it when working with server rendered pages.
Do you prefer ajax to fetch for some particular reason? as BE dev I'm bit lost in these things, so I will be glad for more insigth into this :)
I sure do. Fetch is too low level for my taste: I don't like having to parse the response for the HTTP code to decide how to handle errors. I almost always prefer jQuery's ajax() method or the Axios library for ajax instead of raw fetch requests. They handle a bunch of things automatically that I'd have to code myself with fetch.
Personally it's been a couple years since I've worked with jQuery. In general I'd say it's only a good thing if you can refactor your code to vanilla use of modern native dom query helpers, fetch calls, etc.
I heard a few years ago that jquery was outdated and wasn't really in use anymore. I usually use plain DOM and created a little function to help me with
document.querySelector()const $ = tag => document.querySelector(tag);Yep, I often use this:
This gives you useful array methods like
filterandmapand works for empty sets, much like jQuery. πYes. No plans to refactor. It makes mine and my developer's lives a lot easier.
Our projects are LAMP stack and don't use modern JS frontends.
I wrote this post years ago about jQuery at the time...
Long Live jQuery
Ben Halpern γ» May 24 '16 γ» 3 min read
But have since come to think that it is effectively no longer needed (I think the
fetchAPI put me over the top). Can you elaborate on what keeps you around the most?Predominantly the readability. I find jQuery a lot easier to read than JS.
I see this site referenced a lot: youmightnotneedjquery.com/ But all it does for me is prove how much I prefer jQuery!
Take the getJson function for example:
jQuery
Javascript
I know which I prefer...
jQuery also comes with the added benefit of
slideToggle()functions,fadeIn/Out()functions, etc.And I can just
$('.classname')to target something, rather thandocument.getElementsByClassName(className)... it's just such an effort to write that much.Time is money, and jQuery helps me do what I need to do quicker ! :)
I appreciate my team and I would need to transition to Vanilla JS if we start to use more frontend frameworks, and we are looking to bring in Vue to some of our projects in the future. But our LAMP systems (Wordpress/Drupal/CodeIgnighter) are still our bread-and-butter projects, and using jQuery in them just makes our lives easier.
I'd also argue modern frontend frameworks are still mostly in their adolescent stages, where they're still trying to stabilise themselves/their role in the future of the web... Vue has been around for 7 years, React 8 years, and Angular only 5 years; whereas jQuery has evolved over 15 years and understands its place in the world.
There is tons of software out there still using it, we use jQuery DataTables and DataTables Editor since they are very polished and work great. We also have a lot of legacy code in production and sometimes a little jQuery can deliver the interactivity we need on the page without needing to use a modern frontend framework with build steps and bundling and all that.
Refactoring also takes time and there is a lot to do and a lot of things that need to be built before there is spare time to refactor things that are working just fine in production and are not overly complex to maintain. You also have to weigh the costs of bringing in complex SPA frameworks, build steps, cicd stuff, and tooling that a whole team will need to learn and that will be around for a while.
We have some web software that is in prod and that is 20 years old. Is there any framework like React, Vue, Angular that are in prod for 20 years with no updates needed?
Not since about 2 years ago, but I got so used to their selector syntax, that I just use
$instead ofdocument.querySelectorin the chrome dev tools - yeah that is already implement in there by default πNope but I think the main point is that hating on jQuery just because it is jQuery is cargo-culting.
That's the point I was trying to make. There's nothing wrong with preferring other tools over jQuery or opting for vanilla JS.
In my sparetime I do not use jQuery. But in my professional work day, it has to be on my toolbelt because our company is supporting applications with over 10+ years lifecycles (public sector clients). So there is no way around jQuery because back in the day what else did we have?
Do I expect this to be refactored? No, unless a customer asks us to do so and pays that job. But why should someone do that? Customers pay for working products - and the product does well with jQuery.
Professionally we'll probably still be using jQuery for a while. We build a large number of sites every year and we have so many types of functionality that rely on jQuery plugins: custom sliders, media lightboxes, form validation, interactive data tables, etc. that it would take a bit of time to figure out compatible vanilla versions. We looked at switching to vanilla JS a few years ago but unfortunately that was before ES6 and the syntax wasn't friendly and we still had to support older versions of IE.
I would love to slowly start updating the code but unfortunately when you have entire design systems built around the existing plugins and we're efficient in terms of building sites, it's hard for us to switch and make the business case for it.
No. I don't work with it anymore and don't have any requirements to work with it.
Simply being that it's unneeded for most of my works, even if I do need selectors there is Document.querySelectorAll.
I work in healthcare tech and a lot of my company's products make heavy use of jQuery. There's been some push to remake some things in React and to start using React for newer projects, but I'm skeptical that it'll actually happen any time soon.
Also in 15 years people will be doing posts like this saying 'do you still use React?' π
I was in a project that used jQuery quite heavily. It was too old, big and complex to get it replaced, the backend and frontend coupling also made any migration idea basically impossible.
Yet, it was really fun to explore ways to insert React in the new pages, cope with React/jQuery conflicts and all that stuff.
So when they add static typing to shitescript (chromescript) the crappy language for manipulating xml documents, are we then to assume you will bin/wrewrite all your current vomit/text files that get transexualised into... normal js?. tadaaa!. js devs are an embarasment. listen to yourself. 40% of the web is wordpress and doesn't care for your crap. were waiting for js to die. Everyone on the planet older than 10 years old know for a fact .js is wank and will be replaced soon as others can target the browser. But apple/google drag heels on purpose to get you on the apps. The webs been stuck in the 90s for a decade and is dying a slow death. Desktop experience is dead.
No. I had extensive experience with jQuery β including rewriting it from scratch (long story) β and I am a big fan of Vanilla.js.
Although I do use πππ½ππ¨ππππ Programming's helper, and I define it exactly that way (verbatim).
Still use it professionally. Frankly I've never worked anywhere that didn't have some legacy jQuery somewhere in the application. As much as I'd love to go through and rip it all out, it's not a business priority and I have enough on my plate.