Revisiting the Hotwire Landscape after Turbo 8
summary
Claims that Turbo 8 significantly reduces reliance on heavy client frameworks and can eliminate a separate front-end build step, demonstrating concrete patterns that stitch server-rendered HTML to Stimulus and CableReady for interactivity. Shows rebuilt widgets and a small dashboard that replace a prior SPA, yields fewer round trips and simpler deploys, and reports the prototype working in production-like tests while reevaluating where StimulusReflex still adds value.
AI-written summary · about
chapters (5)
- 0:00Hotwire and Turbo 8 intro
- 5:20Turbo 8 changes
- 12:31Hotwire approaches vs trade-offs
- 21:52Hotwire future steps
- 28:56Q&A
related talks
29mRevisiting the Hotwire Landscape after Turbo 8
30mThe Future of Rails as a Full-Stack Framework powered by Hotwire
23mReact-ing to Hotwire
32mHotwiring My React Brain
34mHotwire Demystified
38mTurbo Frames Explored... for Fun and Profit
45mTurbo-Powered Web Apps - Modern Web Applications with Plain HTML
25mRails frontend: 10 commandments and 7 deadly sins in 2025