2 ms·

Of course you can combine the two but why use three tools (SSR + HTMX + JS) when I can just use two (SSR + JS)? My point is that if you are going to use a JS f

Of course you can combine the two but why use three tools (SSR + HTMX + JS) when I can just use two (SSR + JS)? My point is that if you are going to use a JS framework then it will do the same as HTMX and I don't have to remember where to draw boundaries of responsibility.

recursivedoubts 2y ago
htmx generalized hypermedia controls, so it makes HTML more powerful as a hypermedia: https://dl.acm.org/doi/pdf/10.1145/3648188.3675127 https://dl.acm.org/doi/pdf/10.1145/3648188.3675127 that means you may be able to express more of your UI needs in HTML, using the traditional REST-ful architecture of the web (HATEOAS, in particular) and reserving JavaScript for the areas where that additional complexity adds the most value. Depending on your application, this may lead to significant reduction in application complexity: https://htmx.org/essays/a-real-world-react-to-htmx-port/ https://htmx.org/essays/a-real-world-react-to-htmx-port/