This is my fourth year doing this update. Some of you may be wondering, "But Brian, didn't you already proclaim Jamstack dead?" Back in July, I did write a post titled "Goodbye Jamstack" in response to the end of the Jamstack Discord Community.
My argument was that, if last year's update proclaimed "Jamstack has become more of a “community” than a set of architectural rules," what happens when there is no longer a place for the community? What happens when everyone filters off into their tool/framework-specific Discord/Slack and there's no longer opportunities to gather and communicate?
But there was nuance to my conclusion that I felt many follow ups missed (emphasis added).
The term seems to be dead but the tools and technologies it encompassed are still very much alive.
Entering 2024, it still feels like the term is on life support, though there may be a tinge of remorse about that. However, the tools that fell under the Jamstack umbrella continue to grow in adoption.
Interested in the tools and technologies of Jamstack? Don't miss TheJam.dev on January 24-25 featuring speakers including Alex Russell, Cassidy Williams, James Q Quick, Matt Biilmann, Zach Leatherman, Salma Alam-Naylor and many more. It's free!
A Brief 2023 Timeline
First, here's a (very incomplete) list of some of the big announcements in 2023:
January
February
March
May
June
July
August
September
October
November
December
The Community Held a Funeral for Jamstack...
In retrospect, trying to convey the nuance between a term being dead and the category of technology it described being dead was always going to be difficult. If it was possible, it appears my post didn't accomplish it because it was shortly followed by a long list of tweets declaring Jamstack dead.
Many folks didn't really seem to see this as a big loss. Tyler from UI.dev declared:
Even though the term was non-prescriptive and imprecise (and thus mostly unhelpful) from the start, Jamstack did help kickstart a movement around modern static sites in the late 2010s. But it was also clearly a marketing term that Netlify overextended to the point where it eventually lost all its original meaning — however nebulous that was to begin with.
Swyx argued that the community was ambivalent about the term, at best, anyway:
The rebrand from JAMstack to Jamstack felt like a distinction without a difference (which is why I continue to capitalize the old way). When the frontend metaframework metagame moved from 100% static rendering to mostly-static to mostly-serverless-and-sometimes-edge, JAMstack’s advocates pivoted adroitly, claiming this fit JAMstack all along, which means it fit nearly everything, which means it stood for nearly nothing. When even a VP is saying ”Jamstack is a feeling”, what he doesn’t say is that feeling is most often ambivalence.
Jared White agrees, arguing that Jamstack's downfall began when it lost sight of the simplicity it offered in favor of complexity that sold services:
Along with this “second generation” Jamstack mindset shift came an order of magnitude more build complexity. Instead of a straightforward CLI kicking off simple transformations to go from Markdown -> HTML plus concatenate some (S)CSS files together or whatever, you’d get multi-minute long builds and GBs of
node_modules...
Publicly, Netlify and its employees (summed up nicely here) responded with a refrain that argued that Jamstack isn't dead, the term is just not necessary anymore because it won. They compared it to terms like Responsive Web Design that are rarely used anymore because they are so ubiquitous that the term becomes pointless. Here's how Matt Biilmann put it:
I would actually argue that Jamstack has won to the point of basically just being "Modern Web Development" by now.
He also clarified to The New Stack:
Very much not dropping the term or declaring the architecture gone!
But, while Jamstack.org still exists, the term has seen a dramatic decline in usage in the community, and is no longer part of Netlify's core messaging.
...But Is the Term Actually Dead?
The term still has strong defenders though, most notably, Zach Leatherman, creator of Eleventy. He started by gathering a number of folks with strong opinions on the topic to discuss it in what he called a Zhuzh and then followed it up with a post on what the future of Jamstack could look like. His goal?
To refocus the definition and pull it back from post-pivot silver-bullet marketing, which was arguably an overstep attempt to pull dynamic/SSR/on-request frameworks like (non-static export) Next.js, Remix, Fresh (et al) under the umbrella.
To that end, he and his colleagues at CloudCannon even launched a new site called The Future of Jamstack. The general idea seems that maybe Jamstack doesn't have to be the solution to everything. Maybe a narrower term closer to its origins can make the distinction of Jamstack versus traditional web development clearer and could revive the community, albeit on a smaller scale.
So Where Does That Leave Us?
Don't it always seem to go
That you don't know what you've got 'til it's gone
I am fortunate that my job gives me the opportunity to talk to a lot of developers and, when it comes to the Jamstack, I could summarize many recent discussions with: "Maybe Jamstack did describe something after all?"
Web development describes an incredibly and increasingly broad spectrum of tools, techniques and technologies. It could mean building full stack applications in a language like Ruby and Rails. Or full stack JavaScript using a tool like Next.js deployed to Vercel (and AWS, Cloudflare, etc. under the covers). Or maybe it's a static site using Eleventy or Hugo that focuses on content but adds some services for dynamic functionality. Or even a simple marketing site built with Squarespace or Wix.
Sometimes these distinctions aren't relevant but most of the time they are. I don't want to go to a conference, join a community, purchase training, buy a book, etc. only to find out that none of it is relevant to me. Web development is just too big an umbrella.
I also prefer that we all don't just further divide off into ultra-niche communities largely run by for-profit companies to support their framework/tools but, unfortunately, that is where I feel that we are right now. It turns out the term, as amorphous as it was, was a nice shortcut for a range of tools and technologies that spanned companies and projects. Trying to reach to a Jamstack audience without it is just laundry-listing a range of things, as I've largely done when promoting TheJam.dev or my Jamstacked newsletter.
Every single data point indicates that everything that arguably sat under the Jamstack umbrella continues to grow is adoption and popularity, but I don't foresee anyone turning back the tide for the term itself. So barring dramatic changes in 2024, this will likely be the last of these updates (note that the event and the newsletter will continue, focusing on that laundry list of topics that are still relevant). Perhaps 2024 will bring us new ways (or terms) to talk about how we build web sites.
Top comments (1)
On the spot, as always :-)