Rails is Obsolete (But So's Everything Else)
summary
Argues Rails’s 2004 assumptions fail for modern single‑page apps that deliver JSON and heavy client logic; cites examples like new Twitter, Gmail, Etherpad and the claim that V8 runs JavaScript up to 100x faster on some benchmarks. Demonstrates a concrete DOM trick: build HTML with innerHTML plus deferred handlers (auto‑generate IDs, insert HTML, then attach closures) to avoid IE slowness. Offers a partial framework sketch, mentions Ruby Racer for server rendering, but no full migration plan.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:52Web Apps Do Not Work the Same Way They Did in 2004
- 2:41Examples of Apps That Work
- 7:01Chrome
- 9:29No Html Apps
- 20:37The Request Response Cycle Is Not Obsolete
- 21:06Url Routing Model
- 28:03How Does Seo Work
- 35:19Conclusion
related talks
32mModern JavaScript, without giving up on Rails Jonathan Johnson
23mRails Frontend Evolution: It Was a Setup All Along
36mRails Vs. The Client Side
34mYour Front End Framework is Overkill - Server Side Javascript w/ Rails
21m6 degrees of JavaScript on Rails
24mThe Rails Features we Loved, Lost, and Laughed at
35mFrontendless Rails frontend
32mAs easy as Rails