The current state of Jamstack is questionable, but the #FutureOfJamstack is bright.

It is no secret people are questioning whether Jamstack is dead or not. A quick google search will lead to many, many, articles, speculating on the current state of Jamstack.

This mostly stems from what seems to be Netlify distancing themselves from the term. They shut down the official Jamstack discord server, and overall seem to be rallying behind a new marketing term. They are no longer the platform of JAMstack, but the Composable web platform.

The term is now free for the community which is a great thing.

The first thing the community established was fuck Capitalism.

A panel of some good authorities on what the Jamstack is, immediatley decreed it anti-capitalist. This is a great message for a few reasons. If something is Jamstack it is better to not have vendor tie in, and this should be a tenant of the community. This doesn’t mean everything you use has to be maintained by a community not attached to a company, we all know by now how the world works. Bills need to be paid.

The Jamstack is portable.

It does mean the tool should not be built in a way that locks you into that company, and this is one of the primary criteria we should use when judging if a framework is worth using.

A good framework is portable this means if I don’t like my host anymore I should be able to pick up my toys and leave. This is by far the part the community can probably agree on the most. I also would add that it should be portable with it’s component types. This is something Astro has proven possible, and I think it is a great thing for every web framework to strive to.

The Jamstack is stable

So portablility is a must, and the further it is pushed the better. The next point the panel made was that is should be immutable but that is much too nerdy, so I think we should say stable. They were thinking about the implementation and not the goal. That is why they are great engineers. However I think the outcome that they want is stability. We want to “build” a website and have it live forever pretty much completely untouched. This belief is pretty core to the movement and is also where our arguments or potential infighting start to stem from.

This makes us want to exclude things like SSR because they can’t be statically stored on CDN’s, and the architecture powering it might update or go down and break. And these are great points, that certainly is a mark against stability. Remember when Flash suddenly stopped working? That was crazy, we don’t want that again.

The Jamstack uses the platform

The panel once again talked about implementation when trying to establish pillars. They put HTML/CSS/JS which is great. I agree with the sentiment entirely. We use the platform. They point out in the comments of the YouTube video that WASM counts, so I think it’s clear the message is to use the platform.

I think that term needs some rebranding too and we can be the ones to do it. To me using the platform means delivereing websites that follow web standards. Like having real form submissions instead of API calls to your own server. Good on Remix, and Sveltekit for that.

This is my personal vote on what pillars we should build the new Jamstack around.

I think the pillars we pick should push us to picking the right technology at the right time, and demand frameworks that allow for this. If your site is mostly freely accessible content it should all be generated at build time. If you have authenticated routes you might have a thin server layer authenticating before serving essentially static pages. If your framework doesn’t allow this it might be better to find one that does.