3 ms·
> by a single server maintaining all the states HTTP is stateless. This is the whole point of the hypermedia paradigm. If you have a page with many partial U
by jonahx 3y ago
> by a single server maintaining all the states
HTTP is stateless. This is the whole point of the hypermedia paradigm.
If you have a page with many partial UI page changes over htmx, then yes, this paradigm puts increased load on the server, but your DB will almost certainly be your bottleneck before this will be, just as in the SPA case.
- jdthedisciple 3y agoI'm not talking about network state, but app state. Yes, in HTMX the server is handling client app state, even things as little as whether a todo is in read or edit state. That just seems absurd to me, let the client take care of that.
- bccdee 3y agoNot really? The server in your example serves the read & the edit components statelessly; the component which the user is viewing exists only on the client.