Fireside Chat
summary
Claims that Rails keeps extracting fewer cruftier layers, that browsers now replace preprocessors, and that Turbo and import maps are temporary crutches; concrete numbers: a real CI test suite runs in 1m12s locally, an industry 15 minute deploy becomes a 2 minute goal with a plausible path to 30 second deploys; built tools and choices include Kamal, moving off S3, favoring SQLite over Redis, and a steady push to collapse distributed stacks into single‑box deployments.
AI-written summary · about
chapters (24)
- 0:00RailsConf reflections
- 1:05Premature framework extractions
- 2:30Web evolution and Rails future
- 5:39Web vs native platforms
- 7:05Webpack in Rails
- 8:28Full-stack Rails developer
- 10:55Hotwire in modern Rails
- 11:59Turbo for browsers
- 13:01Browser innovation and DX
- 14:03Deployment regression to CI
- 16:1015-minute deploys unacceptable
- 17:56Deploys in 30 seconds
- 21:50Build pipeline complexity
- 22:53Rails full-stack simplicity
- 25:22Rails simplicity for solo devs
- 26:47Rails omakase defaults
- 31:04Database sharding and hardware
- 32:30Running everything locally
- 34:36SQLite and Solid Queue
- 37:24Decentralized resilient systems
- 38:47Leaving the cloud
- 41:39AI in Rails today
- 45:28AI future in Rails
- 51:29Rails features ranking
