HTMX strikes me as a good solution when all a web page needs is what HTMX can do. But as Mr HTMX says, "of course" one can do a lot more with JS. And now I have to learn HTMX, which even its author says will need that significant list of add-ons in real-world applications. So HTMX is not even a solution on its own, we need a little ecosystem built around it, and every dev will come up with a different eco system. The fact that its own author sees it as incomplete kinda ruins the "Hey! Just use HTMX!" story. Instead we have the "I hate JS" story. In that case, in my and Westrate's experiencce, fine-grained reactivity is so powerful that we stop worrying about coding. All higher-order expression is declarative, reliably animated by reactive engines. Great fun, I should say. What happens when that web page succeeds so well that more and more functionality is asked of it? I am reminded of dancing bears. https://en.wikipedia.org/wiki/Tame_bear "The marvel is not that the bear dances well, but that the bear dances at all." HTMX fans may not be seeing the flaws in its choreography.
Not to mention, we have CLSJ, not JS, so there is a lot less to hate. 🙂 Thanks for the heads up on #membrane Love seeing WebGL in there. Reminds me of when I used OpenGL on the desktop to come up with a universal GUI. But then the Web came along (without WebGL at first) and I shifted to "JS/qooxdoo Over teh Wire" from Common Lisp.