If It Bleeds, It Leads
summary
Claim: Rails has drifted toward complexity, trading simplicity for layers of indirection. Evidence: seven to ten competing authentication gems, multiple repository/data-mapper libraries, and a surge of small gems that hide wiring behind indirection. Tools examined: data mapper patterns, ROM (ruby object mapper), edr and a tiny gem called vertice. Attempted builds: an EDR-based repository makes domain objects repository-aware and therefore fails the isolation goal. Conclusion: Rails makes the first 80% fast but struggles with complex domains.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 1:00DeCamp
- 2:00Where this talk came from
- 3:00Tight coupling
- 4:10History lesson
- 4:50Spring Framework
- 7:30Rails
- 8:40Heuristic Problems
- 9:45Overabundance of Options
- 10:10Paradox of Choice
- 11:00Convention Based
- 11:30Citing Studies
- 12:30Effective Advertising
- 12:55Obsession with New
- 13:20Patterns
- 14:20Automation
- 14:50Rails Patterns
- 15:20Whats Wrong with Rails
- 15:40Refactoring
- 16:10ActiveRecord
- 16:30TableDataGateway
- 17:00Simple Complex
- 17:15DataMapper
- 18:05DataMapper with Space
- 18:25ActiveRecord Library
- 18:40Repository Pattern
- 19:30Entity Data Relationship
- 21:30Array
- 21:45virtus
- 22:30Data mapper
- 24:15Spring
- 25:40Rails Framework
- 26:40Rails is almost 10 years old
