DEV Community


markdalsaso profile image
Mark Dalsaso • Edited

I believe there is now mainstream agreement that jQuery has no place in a greenfield project. Of course, there are always caveats but I tend to take a pragmatic approach.

If you're are building a new flagship-type product, from scratch or as a rewrite, and targeting stuff like SaaS, SPA, native hybrid, etc., don't even think about jQuery, or anything that depends on it; bootstrap's js components, Kendo UI, etc. Do what you have to do, train-up your team, bring in consultants, whatever.

I believe adding jQuery to a big new greenfield project is a disservice to your organization and to jQuery itself! jQuery has influenced so many things, no doubt it's awesome, and out of jQuery's strengths and shortcomings comes major advances in JS/ECMAScript, Web Components, ES Modules, ....on and on.

Now if you're really good with jQuery, (or say Kendo UI and Bootstrap) and you need to whip something out quick, then there is still value in it. Of course, the problem with this is that once a piece of software gets used, there is a high probability that the user(s) will call for additional functionality; leading to further reliance on antiquated patterns and techniques.

Like with all disciplines, technologies and methodologies advance; the world of web application development has simply moved beyond jQuery. Interestingly, its demise is a product of its own success. There is a huge body of knowledge (blogs, tutorials, videos) of why this is. I tend to lump it all into ROI and software sustainability; the new ways are more durable and adapt better to stuff like feature creep.