If web interface is an application backed by a remote state HTMX falls apart.
If web interface is an application backed by a remote state HTMX falls apart.
What does that mean?
its also the perfect opposite of "true web3" and ethereums original vision, where you load all static assets from ipfs, most app logic is client side and the server or blockchain only comes in (json api, no html fragments or full pages) when you need to interact with other users. still believe in it even after the crypto bros took the name for a bunch of scams and hosted everything on cloudflare anyway. the only thing they have in common i could find is no bundling but for different reasons - everything on server vs compiled libraries shared between apps.
https://en.wikipedia.org/wiki/Gish_gallop
Here are a few brief replies:
popups/tiling - use `<dialog>`
real-time chat - use websockets
slow/unreliable connections - well yeah this is a problem for any app...if you're delivering a 2MB paylaod to start the web app so that it doesn't need a connection, you're just betting that the user has a fast connection initially. what if that's not true either? back to square one. REST/Hypermedia encourages sending small payloads and working within those real constraints
I have no idea what you're talking about with "true web3 and ethereum". HTMX has nothing to do with web3 or crypto.
Every project I started with alpine.js eventually transitioned to something heavier because it was hard to maintain once you're having something more interactive than an accordion or sliding drawer.
I guess it's easier if you move all client logic to server, but I didn't want backend to know about web representation details.