Making a difference with Turbo
summary
Turbo adds a declarative morphing refresh mode to Turbo that diffs and applies minimal DOM changes (using the idiomorph library) so scroll, focus, CSS transitions and cached images stay intact. Applied to a new Hey calendar card table, it replaces 100+ lines of custom stream code, simplifies broadcasting by sending a single page-refresh action, and preserves dynamic frame content via data-turbo-permanent. Prototype runs internally, upstream PRs land in turbo and turbo-rails.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 7:59Turbo’s foundational idea
- 13:20Challenges with partial updates
- 17:18Introducing page refresh with morphing
- 22:39Demo of morphing in card table
- 25:33Simplifying broadcasting with page refresh
- 28:42Preserving DOM elements during morphing
- 30:50Pagination with morphing
- 31:58Recap and future of Turbo
- 37:22Q&A and closing
related talks
38mTurbo Frames Explored... for Fun and Profit
45mTurbo-Powered Web Apps - Modern Web Applications with Plain HTML
32mHotwiring My React Brain
32mRevisiting the Hotwire Landscape after Turbo 8
32mRevisiting the Hotwire Landscape after Turbo 8
14mRails 5, Turbolinks 3, and the future of View-Over-the-Wire
43mTurbo Boosting Real-world Applications
37mDungeons & Dragons & Rails