[welearnednothng]

It absolutely is. Turbolinks’ bad rap is from earlier days and was partially due to just a different JS landscape where certain patterns relied on a hard refresh to not have memory leaks as you change page, or other odd behaviors.

I was one of many devs that would always setup new Rails projects without Turbolinks. Last year, I started a new product at work with a slim team and an eye on simplifying our tech and processes. This included giving Turbolinks and Stimulus a try.

Long story short, it was simple and straightforward and has a notable impact on perceived performance after the initial page load. We had a great experience with it.

These days with Turbolinks 5 it’s quite straightforward. There are some gotchas, but the readme covers various edge cases pretty thoroughly.

Since that project, I’ve gone solo and am working on my own commercial endeavor - and while I’ve been building large scale SPAs since before they were called RIAs, my new product is sure enough using Turbolinks (+ Stimulus).

My understanding is that Turbolinks 6 is coming soon that should be better, still.