Ruby after Rails
summary
Claim: Rails-style server rendering is declining as apps become API backends and client frameworks grow, but Ruby itself persists. Evidence: existing alternatives JRuby and Celluloid exist yet concurrency needs VM features — deep freeze deep copy ownership transfer — plus concurrent data structures and a memory model. Observations: ActiveRecord callback complexity (uploader: ActveRecord::Base callback spaghetti) drives people to other languages, a diaspora spreads ideas back to Ruby, and a community-focused site called human development is launched.
AI-written summary · about
chapters (13)
- 0:00Start
- 4:09TDD IS DEAD
- 6:19POLARIZING STATEMENT
- 14:15Readability
- 15:25CONCURRENCY STORY
- 15:59JRuby Celluloid
- 16:29Deep Freeze
- 17:05Ownership Transfer
- 17:15Concurrent Data Structures
- 18:18RAILS IS DEAD
- 24:38POWER CREATE.
- 27:40intensely human language
- 29:15SHAMELESS PLUG







