Rails Frontend Evolution: It Was a Setup All Along
summary
Argues Rails’ “retreat” was strategic and shows concrete turns: Rails becomes a reliable backend as Rails API gains traction; the Asset Pipeline and later Webpacker introduce JS tooling but hit a complexity wall; HTML-over-the-wire Hotwire plus Stimulus and importmap removes SJR security problems and restores fast full‑stack workflows; Inertia.js provides a bridge used in Laravel; a community gem turbo_mount embeds React/Svelte components with near‑zero boilerplate so complex widgets still work.
AI-written summary · about
chapters (11)
- 0:00Rails frontend evolution intro
- 1:47Foundation of Rails frontend
- 5:23Early JS helpers and RJS
- 8:19JS ecosystem and assets pipeline
- 10:47Rails API mode potential
- 11:51Rails as backend only
- 14:02Hotwire for server-driven
- 17:21Hotwire + frontend components
- 19:07InertiaJS bridge
- 21:41Choosing the right path
- 22:26Closing remarks
related talks
34mFrom Sprockets to js-bundling: Evolution of JavaScript tooling in Rails!
35mFrontendless Rails frontend
36mFront-End Sadness to Happiness: The React on Rails Story
52mRails X
36mRails is Obsolete (But So's Everything Else)
19mFrontend Meet Backend Get Along
25mRails frontend: 10 commandments and 7 deadly sins in 2025
31mReact on Rails