3 ms·
agreed: htmx is good for "swap out this one element and its children". It is not good for "and these other related elements need to update"
by sethammons 2y ago
agreed: htmx is good for "swap out this one element and its children". It is not good for "and these other related elements need to update"
- yawaramin 2y agoTo a certain extent, it works, but there's definitely a point of complexity that you can hit in the app at which it becomes painful. Those are the kinds of apps where htmx is just not a good fit.
- wild_egg 2y ago> It is not good for "and these other related elements need to update" That seems a bit backwards, no? Why can't those other elements manage their own updates? You can have the server respond with an `HX-Trigger` header to dispatch an event and any elements that care about that event can listen for it. Far simpler than trying to coordinate surgical DOM updates in a single HTTP request. Events form the backbone of the browser environment and leaning into that model makes a lot of things much easier