The Great Rails Refactor
summary
Explains the Rails/Merb merge roadmap and concrete engineering work: Rails 3 adopts action_orm proxies for true ORM agnosticism (two integration options for ORM authors), MERB 1.1 absorbs that work, Rack-based middleware and a forking server runner land, and an instrumentation plan called orchestra standardizes events for tools like Rack::Bug and New Relic. Profiling shows callbacks cost ~20% of runtime, so a callbacks compiler replaces iteration with inlined method calls; action_dispatch and abstract_controller refactorings modularize controller code for easier swaps and performance.
AI-written summary · about
chapters (30)
- 0:00Intro
- 0:13Merge
- 1:21Solo
- 4:00ActiveRecord @obj
- 4:50Two valid interfaces
- 5:06Better than it looks
- 7:04Two Options
- 7:231. Compliance
- 8:08Code Change
- 9:44Community Extensions
- 14:26Rails 2.3
- 15:08Failsafe
- 15:47Controller#call
- 16:26Endgame
- 17:50Refactoring
- 18:24Unification
- 20:26Compilation
- 21:51Action Pack
- 24:00Action Dispatch
- 25:48Abstract Controller
- 26:59Ability to super
- 28:25Public API
- 30:55Debugging
- 31:15Pluggable
- 31:26Orchestra
- 32:52New Relic
- 33:49Exception Middleware
- 34:58Competition
- 35:36Known Interfaces
- 35:57Rails Boost
related talks
48mFrom Rails to Rack: Making Rails 3 a Better Ruby Citizen
01h 09mRails 3 ...and the real secret to high productivity
01h 03mStrengthening the Ruby Ecosystem Part II: Merb
35mExploring Merb
55mThe Future of Rack
41mWriting Modular Ruby Code: Lessons Learned from Rails 3
30mRails Sojourn: One Man's Journey
38mRails 3.1 Whirlwind Tour