Ten Years of jQuery and Beyond

Posted on by

On the 14th of January 2006, John Resig went to an event called BarCamp NYC to talk about some of the projects he was working on. One of those projects was a JavaScript Library called jQuery. It was the birth of what has become the most widely used JavaScript library ever written.

It’s hard to imagine now, but there were already about a dozen JavaScript libraries around on that day when John announced jQuery, trying to solve basically the same problem. There was no guarantee that yet another library was needed, or that jQuery would go anywhere. Yet slowly and surely over the past decade, jQuery has been widely adopted. It’s hard to find a web developer today who doesn’t know it, or a web page that doesn’t use it.

Code alone isn’t what made jQuery unique and drove its popularity. It took a strong community of users and contributors who pitched in to help newcomers master the library. John made a point of listening carefully to the community and incorporating feedback from those interactions which made both the code and documentation better. jQuery was shaped by the people who used it and appreciated the way it simplified development across multiple browsers. What makes this story even more remarkable is that it all began in an era before Github and StackOverflow!

Based on the experience and community insights that arose from jQuery development, the jQuery Foundation was formed in 2012. It included not only the jQuery projects but tools for other parts of the development lifecycle such as QUnit for testing and Globalize for internationalization. Last year, we joined with the Dojo Foundation and expanded the set of projects we support to include Dojo, Grunt, Lodash and more.

The Foundation continues to be guided by the principles that made jQuery a success and advocating for things like inclusiveness, diversity in teams and empowering contributors to lead within the open source community. As we move into 2016 and the number of projects we support grows, so do the ecosystems being built around those projects. An ecosystem thrives when its projects collaborate and share core principles. By enabling that collaboration, we hope to encourage new ideas and different points of view in open source JavaScript.

In Internet years, a decade is an eternity; web development has changed immensely in that time as has the web itself. Yet the basic formula for success in an open source project has been constant: start with a good idea, adapt it to the needs of users (even as those needs change), and get the community involved in all aspects of the project. Let’s measure our success not in the code that we write, but in what users create using our code and how it inspires them to push the web even further.

Here’s to another decade of awesome open source innovation in JavaScript!

17 thoughts on “Ten Years of jQuery and Beyond

  1. Francisco Ramos on said:

    … and today I’m wondering what the future is for jQuery. I have stopped using it two years ago, when we dropped support for IE8. There is no londer need to use it for DOM manipulation (the browser DOM api is enough) and for other tasks sometimes I resort to lodash. Current frameworks no longer use it either… I don’t miss it, and neither do most of my peer developers.

    What’s the future of jQuery?

  2. Nugzar on said:

    What are you talking about, man?
    Whole web use jQuery:
    Angular, Bootstrap, the thousands plugins,
    libraries and frameworks use jQuery!
    I would not be surprised, if you use jQuery, but do not know about it!

  3. Francisco Ramos on said:

    I’m talking about the fact that I haven’t used jQuery for over 2 years, and still I’ve been able to build quite impresive web apps with simple JS, HTML and CSS… that the DOM api is enough for DOM manipulation… that there less and less cross-browser issues that need to be addressed. The more powerful HTML5 becomes the less need for jQuery.

    I think developers should not rely on this library anymore and embrace the power of the browser API… I have interviewed tons of Frontend developers, and many of them are so dependant on jQuery that they can’t do simple things like toggling a class without using jQuery. Most of them don’t even know that arrays have native map and filter functions. And these are just two examples. Many woudn’t be able to work without this library. Those are what I call “jQuery Developers”

  4. Francisco, you are talking about 2 slightly different things..

    There are the Web APIs and then there is JavaScript

    jQuery and such libraries makes life easier by abstracting Web/DOM APIs. DOM APIs are inconsistent, hard to read, easy to make typos and plain inelegant.
    These APIs will remain that way till the end of time.. and so, jQuery will always be relevant. But you are right, DOM API is enough for DOM manipulation and most of the cross-browser issues have been ironed out, but most devs do not like working with these verbose, java-like APIs

    As for JavaScript (since you mentioned arrays), it has been mostly consistent on all browsers and I dont think jQuery addresses this as much sans its small set of helper methods under Utilities