Comment by bradgessler
4 months ago
I recently finished shooting a video course for Phlex and I found that naming the Turbo Stream section at https://beautifulruby.com/phlex#unit-5 was the most challenging because of Turbo Streams and Turbo Broadcasts.
My recommendation: Turbo Drive & Pagemorphs are what most people should use for most problems. Drive reduces flickering between page loads and Pagemorphs list to channels on the server to reload the page if something changed.
I think Turbo would benefit from positioning itself more closely to Rails and simplifying the terminology. If you look at the https://hotwired.dev website, you won’t find Rails and you’ll find a bunch of words like Stimulus, Drive, Streams, Broadcast, etc. The docs aren’t entirely coherent either.
What do you mean by “Pagemorphs”? A quick Google search suggests you’re the only person using this term so it’s hard to know what you’re recommending. I think it must mean e.g. https://turbo.hotwired.dev/handbook/page_refreshes?
Been using Turbo (and Turbolinks before it) for 10+ years, mostly outside Rails. It's awesome in that context.
Can't really see how making it more Rails-centric would help - more likely it'd just cause a fork for everyone using Hotwire without Rails/Ruby.
Any plans for purchase parity for South East Asia?
Shoot me an email, brad@beautifulruby.com
Exactly that.