I use both htmx and turbo extensively in production, but my preferred choice is HTMX + HS. 1. with Turbo you are basically opting in to use "former-turbolinks-approach" on all links. If you prefer html-first approach to website development you may not find this comfortable. I like spending time building stuff as opposed to constantly debugging what standard browser behavior we broke again (history, back, forward, refresh etc.) 2. HTMX is explicit in what you want to replace and you define this right where you expect this to be defined - in the html part of a given link, button etc. Turbo adds a bit more magic in Rails but that can backfire as you may get lost trying to untangle what exactly is going on - especially if you come to the piece of code after some time. 3. You get features that are actually very useful like debouncing - built into the HTMX 4. HTML, Tailwind, HTMX, HS is truly powerful combo if you like "Locality of Behavior " and you may find you dont need anything else really, on the front-end 😉