Tech entrepreneur. Founder @electricsql. Founder @gatsbyjs (acquired by Netlify). @kylemathews on Twitter

I feel like I’ve never really grokked static site generators despite chatting a lot with @kam (of Gatsby fame) about them. They now seem like a ecosystem that’s *more* complex than WordPress. But what’s the essence of them, the way “chronological web log + rss” was it for WP &co? https://jamstack.org/generators/

Blogger at ribbonfarm.com, running summerofprotocols.com, host of /gloom ☀️

I feel like there’s something more fundamental behind the programmer affordances of the JAM stack over LAMP and ability solve for specific metrics like speed (which Gatsby solves for). I know what I’m giving up (low/no code dynamic interfaces) but *why,* broadly? Is there a media philosophy I’m missing?

People like that, in theory, everything is hot swappable. If one service doesn’t work or shuts down you just plug in something else. I’ve seen a number of RFPs lately where client wants to remove dependencies on big platforms, thinking they’re de-risking.

thought scavenger. corporate trickster. software designer. here to fart around. bryanking.blog

Not in my experience. Every vendor and open source project has different standards so it’s never as easy as “just changing the API call”. And usually any switch comes with some desired change in functionality, what JAMstack ppl say is a one day plumbing project is often a quarter-long renovation.