Htmx 4.0

Let's be real: a major version bump for htmx is not the same as a major version bump for React or Angular. When Meta or Google bump a version, it's usually an excuse to break APIs, add a new compiler, and force developers to rewrite everything for the third time this year. When htmx bumps a version, it's a statement that the core philosophy—hypermedia as the engine of application state—has been refined, not reinvented. That's the kind of stability the web actually needs. The move to four.htmx.org is telling. It's not just a new domain; it's a declaration that this project has legs beyond the initial "cute underdog" phase. htmx has spent years being the scrappy alternative to the SPA monoculture, the library you cite in arguments before someone calls you a luddite for not using Next.js. Now it's on version 4, with a dedicated site, a thriving community, and a release that the HN front page actually cares about. That's not a fad anymore. That's a movement. The HN reaction is the real story here. 647 points and 164 comments isn't just interest—it's a battlefield. Every htmx release brings out the usual suspects: the SPA defenders insisting you can't build a real app without client-side routing, and the hypermedia true believers pointing out that your "real app" is 90% forms and buttons. The debate is exhausting and necessary in equal measure. htmx keeps shipping regardless, and that's what matters. What remains to be seen is whether htmx 4.0 can convert the unconverted. The library has already conquered the "I'm tired of JavaScript" demographic. The next frontier is the mainstream developer who's been told for a decade that you need a framework to do anything interesting. If 4.0 delivers on the promise of even smoother server-side interactivity and WebSocket handling, it might just pull a few more souls out of the SPA vortex. Either way, the hypermedia heresy is now officially a religion with a version 4.0. Praise be to the humble ``. Source: [https://four.htmx.org/announcements/2026-08-