jQuery has been the basis of our front end JS for a number of years. The key part for us was that the amount of code saved by using jQuery methods, as opposed to writing out cross-browser compatible alternatives made it a no brainer. In recent years we've had to be clever in how we deliver jQuery on the websites, to ensure it's not render blocking and improve client-side performance but it's still a vital library.

In process of Learning Technics. Cross-browser Compatibility: handles a lot of infuriating cross-browser issues . used to make some widgets and effects: jQuery plugin repository.

jQuery allows to easily do DOM scripting (i.e. HTML elements manipulation and event handling). using jquery under MVC webapps. Studing to know more

jQuery is only used in small amounts, primarily for animations and UIs, but it is included in the WSC, so we felt like not including it here would be kind of cheating. jQuery also almost makes ajax-requests a pleasure to work with, so ... you got that point, jQuery.

I don't use javascript, I use jquery....well I know it does not make sense, but I just want to stress how important it is. let's rephase it: whenever I use javascript, I use jquery. when you look at any js file of mine, 90% is jqery api.

"Idiot proof MVC" using transactional pub/sub between models, views, and controllers to establish reliable one-way data flow. Combines well with Polymer web components to create a modular, loosely coupled front-end architecture.

Used jQuery for dom manipulations. Another great feature used was its deferred() function with promise to avoid callback hell.

What is the Flux Application Architecture?

I'll consider Zepto if jQuery is overkill for the amount of JavaScript work I'll be needing for the specific project.

For the occasional lightweight JQuery alternative.