Rails 2.0: It's done!
Rails 2.0 is finally finished after about a year in the making. This is a fantastic release that's absolutely stuffed with great new features, loads of fixes, and an incredible amount of polish. We've even taken a fair bit of cruft out to make the whole package more coherent and lean.
Context & Ripple Effects
The release lands mid-argument about Rails' direction. In August, creator David Heinemeier Hansson told InfoWorld that "less is more" was deliberate Rails strategy, and weeks later a widely read O'Reilly Ruby post on switching back to PHP crystallized the developer-friction critique. Rails 2.0's emphasis on removing cruft reads as a direct answer to both threads: coherence and polish positioned against feature bloat.
Syndication across InfoWorld and OSDir shows the release traveling well beyond the core community, which matters because Rails' growth case at this point depends on converting curious mainstream developers, not serving the insiders who already know the tricks.
First-order effects
- Existing Rails application owners face an immediate upgrade decision: 2.0 removes cruft by design, meaning apps built on pre-2.0 conventions need review before they benefit from the polish.
Second-order effects
- The defection narrative gets harder to sustain — the PHP-backsliding argument rested partly on Rails' roughness, so a leaner, more coherent release forces critics like the PHP-return camp to argue on tooling fit rather than quality.
Third-order effects
- The release reinforces a structural bet in framework competition: winning by curating fewer, better defaults instead of accumulating features, making 'opinionated design' the axis rivals must respond to.
The trend: Web frameworks are shifting their competitive ground from raw feature counts toward curated simplicity, with Rails 2.0 as the clearest statement of that doctrine.