React-ing to Hotwire
summary
A standalone React/Redux app with re‑kit tooling gets migrated into the Rails monolith using Hotwire and Turbo Frames plus Stimulus, cutting dual deploys and roughly halving server costs. Client‑side state and loading boilderplate disappear, replacing API juggling with server‑rendered fragments. The proof‑of‑concept converts sprinkled admin pages first, the full rewrite finishes in about four months, and the replacement stays in production and continues to be built on.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:58React maintenance crisis
- 10:19Convincing management to Hotwire
- 13:32Hotwire simplified frontend
- 16:23Stimulus and dynamic UIs
- 17:47Turbo Frames and Streams
- 19:35Hotwire’s Rails simplicity
- 20:18Lessons learned with Hotwire
- 21:43Project outcomes
related talks
28mOverreacting—From React to Hotwire
32mHotwiring My React Brain
30mThe Future of Rails as a Full-Stack Framework powered by Hotwire
31mReact on Rails
32mRevisiting the Hotwire Landscape after Turbo 8
36mFront-End Sadness to Happiness: The React on Rails Story
23mRails Frontend Evolution: It Was a Setup All Along
31mReact.js on Rails