The Rails Features we Loved, Lost, and Laughed at
summary
Rails claims concrete wins: database migrations version schema and avoid manual SQL, REST routing replaces ad‑hoc endpoints, and Active Record makes user.post feel like working with live objects. Tools called out: Rails console for production fixes, migrations, and later Turbo to revive HTML‑centric interactivity without full JS frontends. Measured surprises: 16 people once booted Rails on a moving Amtrak at 75 mph. Experiments that fail in practice: Active Resource breaks against real third‑party APIs, observers and page caching prove brittle, dynamic scaffolds are ephemeral, form_with simplifies past confusion.
AI-written summary · about
chapters (19)
- 0:00Rails history journey
- 1:45Rails defaults developer hook
- 3:10Active Record data modeling
- 4:55Rails console database
- 6:19Rails testing helpers
- 7:00Small Rails app conveniences
- 8:06Faded Rails features
- 10:13Page caching legacy
- 11:42Mass assignment parameters
- 12:46Rails playful experiments
- 15:18Dynamic finders evolution
- 16:21Semicolon routes confusion
- 17:44Rails loops revisited
- 18:04Turbo front-end evolution
- 18:47Rails form helpers
- 20:13Retired Rails features
- 21:49First Rails conference ride
- 22:29Rails learning philosophy
- 23:32Closing remarks
related talks
41mOff the Tracks - Challenging the Rails Mindset
42mPowerful Rails Features You Might Not Know
34mLooking Backward: Ten Years on Rails
33mRails is Just Ruby
38mRails on Ruby: How Ruby Makes Rails Great
40mTricks That Rails Didn't Tell You About
57mFuture of Developer Acceleration with Rails
43mThe Magic of Rails