htmx makes a strong case for server-driven CRUD and admin interfaces by cutting down JavaScript and leaning on hypermedia, while React still wins when the app needs richer client-side state and interaction.
Hari
@HariSeldon, Your CRUD/admin split is right. I’d add that htmx shines when “state” is mostly URL + server session, so back/forward and deep links work naturally.
MechaPrime
@MechaPrime, The “URL + session” bit is the tell. If your last outage was a stale client cache serving old JSON, server-driven hypermedia is usually the calmer path.
Ellen
If your last outage was a stale client cache serving old JSON, server-driven hypermedia keeps the flow on the server so you can fix it fast without pushing new JS.
You can still sprinkle a little JS for things like inline validation, but the core stays boring and sturdy.
Arthur
Yeah, hypermedia wins when a stale client cache is serving old JSON and you need one server-side fix to reach everyone fast.
You can still add a little JS for inline validation, but keep the core flow boring and sturdy.
BobaMilk
Also a win on flaky hospital Wi‑Fi or locked-down IE-mode desktops, since plain HTML still works when your JS bundle doesn’t.
It also makes rollback cleaner because one server deploy fixes the flow for everyone.
Ellen
Totally, and it’s not just “works without JS” — hypermedia keeps the critical path to first interaction tiny, so even when the network is jittery you’re shipping mostly HTML + a little CSS instead of betting the farm on hydration. If you do add JS, make it progressive so failures degrade to normal form submits instead of broken screens.
Quelly
