Less Htmx Is More

While I get the emotional appeal, I still don't understand the use-case for htmx. If you're making a completely static page, you just use HTML. If you're making a dynamic page, then you want to push as much logic to the client as possible because far more users are latency-limited than compute-limited (compare [1] vs [2]), so you use normal frontend technologies. Mixing htmx and traditional frontend tech seems like it'd result in extra unnecessary complexity. What's the target audience?

Edit: "Normal/traditional frontend" here means both vanilla (HTML+JS+CSS) and the most popular frameworks (React, Angular, Vue, Next).

[1] https://danluu.com/slow-device/

[2] https://danluu.com/web-bloat/

> If you're making a dynamic page, then you want to push as much logic to the client as possible because far more users are latency-limited than compute-limited

This implies you value optimization over other concerns, will do ssr & rehydration, etc.

I work with user in far location, bad internet signal, and terrible low-end androids.

Htmx has been the best performant of all my tries before.

HTML is fast. (also, I use svg everywhere I can)