You make good points. And these are different use cases, where one is simple client behavior where JS is suitable, whereas the other needs a round trip anyway.

You make good points. And these are different use cases, where one is simple client behavior where JS is suitable, whereas the other needs a round trip anyway. I wouldn’t go as far as 99%. There are a lot of web apps where you toggle between panes, expand certain things, and so on. But I think you are still right in the sense that htmx is a very fruitful starter kit that can cover many if not most “boring” standard use cases. One thing is for sure, this SSR hydration shit show is not a good state of affairs. It’s way too much complexity for what it does. And now you have to worry about reaching the same logical state from two different starting points. > I'm betting that you can make a whole interactive site on top of Go's html/template library + htmx, using a pattern I'm developing This is cool, and indeed reminiscent of PHP. Cycle of life!