> I know people loved turbolinks, but the very thought of it gives me nightmares. Is it really that bad? With Turbolinks 5 (and its successor Hotwire Turbo Dr

> I know people loved turbolinks, but the very thought of it gives me nightmares. Is it really that bad? With Turbolinks 5 (and its successor Hotwire Turbo Drive) you can do nothing except add 1 line of JS to your application and reap massive wins in terms of page transition speeds. And this all works without changing 1 line of code on the back-end and it works with all tech stacks. IMO it's the biggest bang for your buck that you can do to make a website feel good with the least amount of effort. And now with Turbo Drive you can do the same with form submissions without needing any back-end code and it also works with every tech stack with no special libraries or work to be done server side. Then Turbo Frames builds upon that to partially update a segment of your page and Turbo Streams introduces websockets for when you want to broadcast stuff or do real-time updates. It's a great system. Use HTTP for everything except for when websockets makes sense.