To summarize some quick search results..
https://htmx.org/
https://turbo.hotwired.dev/ https://stimulus.hotwired.dev/
https://alpinejs.dev/
https://unpoly.com/
---
> - htmx if you want to stay as close to framework-less HTML as possible
> - unpoly if you want a bit more structure and functionality out of the box
> - hotwire if you want stuff to "just work" and not get down into the details of your HTML so much
> "I think unpoly wins over all other alternatives as it provides a lot.more features and also its API makes a lot more sense"
https://www.reddit.com/r/django/comments/ppuguf/how_does_htm...
---
> For anyone wanting a "SPA" like feeling of their apps without having to deal with all the SPA complexity, and not starting from scratch or being able to rewrite their applications, try Unpoly. It is really great and very underrated.
---
> hotwire is the best option if you're using Rails. From what I know, hotwire needs a lot more of backend "collaboration" than Unpoly
> Alpine.js is an aberration. Writing code inside html attributes is a fantastic way to break every editor templating language plugin, syntax highlighting, etc.
> unpoly handles a lot more use cases, and it feels a lot more "declarative"
> Unpoly is kind of the "django" or "rails" in this category of tools. It gives you a lot of stuff. From page transitions loading progress bar (a'la turbolinks) to ajax replacing links, to modals, to popups to sidebars, to automatic blocks replacement (up-hungry) to form posts, to handle error responses, layers, polling.... and it has an awesome way of writing your own "components" with the up.compiler api.
> the only reason Unpoly isn't the most popular solution in this space is because of bad marketing.. I really think it is the best (if you're not using Rails, then I'd use Hotwire+Stimulus+etc...).
https://news.ycombinator.com/item?id=28625500 How Unpoly differ from Hotwire (Turbo+stimulus) or htmx+alpinejs?