The decline as per SO:

thenextweb.com/creativity/2017/05/09/stack-overfl…

No, because javascript became cross browser and after the introduction of the css3, jQuery lost big part of his glamorous. The new generation libraries are more aimed on architecture and performance because the new generation apps are bigger and more complex.

Will it still be on websites in 10 years? undoubtadly yes... willit be quite as common as to what it is now? unlikely.

The trend on the development community over the past few years has turned to the opinion of "people use jquery when they do not really need it", sites like 'youmightnotneedjquery.com' have emerged to educate the droves of users who are reliant on it.

Now, no one is saying jquery is bad - its an awesome tool, and it also helps to eductat many in a friendly way about some JS fundamentals that probably steers many careers.

But, larger libraries are now handling DOM manipulation themselves (sometimes even with jqueryLight, in angular for instance) react handles its own virtual dom - so i agree we will see less numbers of developers using jquery but many will find it hard to leave out of their toolkit some time yet.

-Steffen

People asked me if Delphi will still be around 15 years ago, I was a huge fan of Delphi using Delphi 7 at the time coming from a Pascal background and since then Delphi has almost vanished into obscurity after Borland dropped Delphi for C++ Builder and Java.

Strange things started happening to it, it started compiling to C# then C# got dropped, then another company (Embarco) took it over and it is still somehow maintained and used by die-hard fans, a lot of them still running on ancient versions of Windows.

What happened to GWT? Back in 2011 Google pulled out of GWT and started working on Dart. Vaadin took over GWT and since Google pulled most of their engineers out of the project, you can see how drastic their release schedule slowed down (a release almost every month VS 2015 only one beta release): gwtproject.org/release-notes.html

Just like with GWT, Jquery was developed to work around browser incompatibilities (especially IE), since browser incompatibilities are rapidly becoming less and less since MS started moving in a different direction, I believe there will be less and less arguments for using Jquery and it will go the same route as GWT or even Delphi, especially if their founders move on to greener pastures; another group / company will take it over and keep it breathing, even if only enough to keep it from going extinct, but it will be dead for all practical purposes.

I love jQuery and 5 years ago I couldn't imagine any web app without jQuery. But today is different - JS, HTML and CSS has evolved a lot, and new frameworks have emerged to solve different needs. Right now I'm working on a SPA web app without jQuery and, surprisingly, I'm not missing it at all.

jQuery is fantastic for DOM manipulation, but IMO, as development in client side became more complex, the need for a more rubust, modularised and flow-control has grown up, and the core jQuery can't help much on that.

If I had to bet on the next 10 years, I'd say that this jQuery we know will just support legacy apps.

jQuery's usage doesn't seem to be declining even with the rise of newer and better-structured libraries out there. If jQuery does not upgrade their feature set, not likely. But being the most easy way to start building something cool, I'd say Yes.

Yes. jQuery is the easiest way to start making something on JS in a browser. The biggest advantage of it is working with collections of nodes (empty or non-empy). Unfortunately DOM allows to work with separate nodes so you need to check for node existence (querySelector) or iterate over method-less NodeList (querySelectorAll).

I guess almost everybody gets start as a JS developer from jQuery.

It is like every other library, there is the pickup: the library catches the eye, solves most of the problems; people love it. Then comes the constant: the library has been the de-facto standard for quite a while, people have been creating all sorts of forks from it, hacking it and whatnot. Then comes the sad part: its decline. People no longer use it. It's good, but only for demonstration purposes. It becomes stale. Not well maintained, and then the core contributor stops developing it.

Not to hurt anyone, but Knockout.js seems to be the perfect fit here. It saw its ups and downs. But now, with the latest technology and their requirements, it's not keeping up so well.

But, let's be an optimist. And take the example of my beloved AngularJS for a second here. It saw its ups, (and downs), but then: some valiant guardians of the galaxy... that was my last Star Trek reference, I promise. The point here is that it's now being actively developed to support the latest features (TypeScript, ES6, etc.)

For jQuery, I have only seen it get more momentum; it hasn't stopped, or slowed down. And remains to be the industry standard in battle-tested, DOM manipulations.

In conclusion, after 10 years, IE may be as good as WebKit; people will start using the trailing comma... but, as far as I think, jQuery "should" (RFC 2119) be the standard. The community is huge, big companies are using it. Who knows? ;)

Talking about such lengths of time is hard to do, but I'll give it a shot. jQuery will probably still exist, but maybe in a different form, with support for the new things that are still to come. But then again, you'll never know if someone will think of something better.

Products and technologies will come and go (as always), but I personally feel that jQuery will be one of the survivors.