HTMX is very interesting, I saw it presented at DjangoCon.

Being involved in a lot of SPA's these days I can't help think that we spend way too much time building complex frontends and managing state.

Anyone feel the same way? HTMX feels fresh.

Any takeaways? Is it a promising direction? Would it be viable to create an “isomorphic rust” web app?

How would you maintain state in the service worker when is shutdown by the browser after being idle for a period of time? Or does Htmx not keep state on the server side in the first place?

What's the point, though? HTMX or any other SGMLish angle-bracket markup template engine is for content creators/authors, not necessarily developers. Sure you can play connect-the-dots and combine technologies picked up from the HN front page, but if you're using heavyweight developer pipelines such as Rust and WASM with service workers anyway, that's already way out of reach for non-developers, and comes with full developer responsibilities for testing, security, maintenance, build systems, versions, dependencies, and whatnot.