I was specifically thinking of modern smartphones in fact, which are pretty damn fast at executing a little bit of JS.
(Though I agree that some of the bloated bundles resulting from modern frameworks or their poor usage definitely go to far)
What's unnecessary to me however is sending bytes thousands of miles across the wire to some server to do the same.
HTML is more verbose, so I would guess that JSON serialization is slightly faster, but I doubt there's an order of magnitude difference. (I could be proven wrong though)
I agree that taking HTMX to the extreme where _all_ interactions require a request to the server is too much overhead for interactive web apps. But there's likely a good middle ground where I can have mainly server side rendering of HTML fragments with a small amount of client side state/code that doesn't incur particularly more or less server load.
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.
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.
Imagine 10s of thousands of clients requesting millions of HTML fragments be put together by a single server maintaining all the states while all the powerful high end computing power at the end user's fingertips goes completely to waste.
Not convinced.