Looking Backward: Ten Years on Rails
summary
A clear before/after: 2004 Java work means raw servlets, JDBC and a long edit‑compile‑deploy loop on WebSphere with inscrutable JSP stack traces; Rails introduces live reloading, a development console, and ActiveRecord and migrations that eliminate hand‑written SQL and let teams evolve schemas. Rails bundles defaults, plugins/gems and promotion into a working product, and it already serves hundreds of millions of API requests a day a month, while Sinatra and Jengo inspire lighter alternatives.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:30Looking Backward
- 4:13Development in 2004
- 7:45Web development in 2004
- 11:03Python
- 16:55Features
- 22:23The Future
- 27:06Micro Frameworks
related talks
31mTen Years of Rails Tutorials
30mThe Rails Story: Two Decades of Design and Decisions
24mThe Rails Features we Loved, Lost, and Laughed at
35mTen Years of Rails Deployment
23mRails Frontend Evolution: It Was a Setup All Along
31mSo Long, Hoboken: Migrating a Huge Production Codebase from Sinatra to Rails
31mThe History of Rails in 10 Blog Posts
28mServices and Rails: The Shit They Don't Tell You