Apparently, jQuery Foundation has morphed into (or been absorbed into newly-created... or something like that...) js.foundation. (I learned about the "apparent" equivalence only from a news article - you'd be hard-pressed to glean that from the official js.foundation website.)

js.foundation has a broader vision, encompassing a good number of Javascript projects, which do include jQuery, jQuery Mobile, and jQuery UI. From the official website, it appears that the "jQuery" parts are being de-emphasized.

I've read some discussion suggesting that jQuery is irrelevant today, as browsers have gradually taken-up support in areas that jQuery has been traditionally used for, and suggesting that today one should be writing to the Javascript APIs. (I think, though, that although browsers do now have close to 100% coverage of what jQuery does, jQuery is a LOT more convenient. And all those benchmarks that are being quoted need to be updated for 3.0.) And/or suggestions that more comprehensive frameworks (typically MVC) will provide for the gaps. I don't find that a very nice choice - between inconvenient-but-fast APIs, and a big, bloated framework.

Any idea what impact this change in administration will have on jQuery, jQuery UI, and jQuery Mobile? Maybe JQUI and JQM are ideas whose time has come and went. But I think it would be a huge mistake to leave jQuery by the wayside. (The way JQM has been - encouraging official statements aside, it seems dead in the water.)

It seems with deep-pocket sponsors (but hasn't jQuery always had apx. the same list of deep-pocket sponsors) there may be new funding, but at the same time, the foundation is taking on support of additional projects.

Are we going to hear something official about how this all affects jQuery?

https://js.foundation/

http://www.infoworld.com/article/3131489/javascript/javascript-projects-regroup-under-a-new-foundation.html