The problem is that you need to remember every single place in your app that needs to be updated when you change state instead of your framework doing it for yo

The problem is that you need to remember every single place in your app that needs to be updated when you change state instead of your framework doing it for you. You said it yourself-- the "out of band capabilities". Instead of your UI automatically updating in reaction to a state change, you have to manually write out every single component's markup while being extra careful to make sure that each ID matches. [1] This is why HTMX is ultimately an imperative framework. You have to wire everything up manually yourself instead of simply building a declarative representation of your UI and letting your framework handle the synchronization. Did you ever use jQuery? The negative aspects are remarkably similar to the point that it is mildly amusing. 1 - https://htmx.org/attributes/hx-swap-oob/ https://htmx.org/attributes/hx-swap-oob/