Rebecca Murphey

Last updated

The 14 days of jQuery

It has been 13 years since the 14 days of jQuery celebrated the release of jQuery 1.4 in January 2010, arguably the major-version pinnacle of the library that shaped the frontend development world for years to come. In 2005, it was magic; in 2010, it was an industry. And in 2023, it has essentially no role on the modern web that it helped create.

It’s fascinating to me to consider whether jQuery was a necessary step on JavaScript’s trajectory: no one would argue today that people should be building large JS apps with jQuery as their sole core, but people had actual disagreements about this back then. Companies and people were internet-famous for their jQuery plugins. There were t-shirts and whole conferences about using jQuery, and whole web sites about how to not use it at all. Ads for frontend devs were written in pseudo-jQuery. A company that called itself “The jQuery Company” proposed to create a jQuery certification. Once I ran a conference and enticed earlybirds with a copy of the jQuery source, signed by John Resig himself.

It was a time, and I don’t rule out that you had to be there. Thirteen years later, I have some questions:

Of course we can’t answer any of these questions, but I find myself thinking a lot about that time these days, and I’m realizing that the echoes I hear aren’t just in my head. This whole data-driven but human-informed focus on developer productivity is in its own primordial soup stage. The ingredients are there somewhere for transformative outcomes, but evolution still needs to do its thing. We haven’t even agreed on what to measure, or how to define “good.”

Indeed, I’m pretty sure we’re not even at the jQuery analog of the journey yet, though not for lack of lots of companies trying. Anyone who’s paying attention knows that the status quo can’t hold, but no one has quite figured out how to put all the ingredients together, in a repeatable way, to get to a breakthrough outcome.

If past does turn out to be prologue in this case, here are some things I think we can anticipate:


If you’ve made it this far, I might as well share that the reason I’m thinking about this stuff is that 1) I can’t help it, it’s my brain; and 2) on Monday, I’ll start a new and very different job from any I’ve ever done, at a small, early-stage company that’s focused on developer productivity. Stripe to startup is going to be a journey unto itself, but I’m still giddy that someone wants to actually pay me to do what I’ll be doing. More soon.

This post first appeared on my Substack, where you can subscribe for new posts.

Read more posts in the archive.