Here’s to the crazy ones
summary
A 2005 team extracts authentication code into a separate repo and ships a small login engine that packages controllers models views and migrations as reusable code and it works well enough that the idea of engines gains traction despite heated debate later absorbed into core: engines functionality lands in Rails 3 (2010) and migrations and assets merge by 2011 and reappears as active storage and popular gems implement engines for auth and CMS use cases.
AI-written summary · about
chapters (10)
- 0:00Start
- 9:40Experimental Plugins
- 10:37The Login Engine
- 13:55The Wilderness Years
- 20:32The Gartner Hype Cycle
- 21:39The Trough of Received Opinions
- 22:25Summary
- 27:14The Rails Way
- 29:14Active Resource
- 31:16The Future of Rails
related talks
22mChecking under the Hood: A guide to Rails Engines
42mDiary of a Mad Rails Engineer
51mRails Engines Patterns
37mCreating Mountable Engines
38mAll you need is Rails (Engines): Compartmentalising your Monolith
35mWrangling Large Rails Codebases
19mBuilding a Rails Engine From Scratch: Active Storage Dashboard
41mMorning Keynote