It's too bad the author doesn't appear to have (virtually) attended the recent Rails online conference (http://en.oreilly.com/railswinter10 http://en.oreilly.co

It's too bad the author doesn't appear to have (virtually) attended the recent Rails online conference (http://en.oreilly.com/railswinter10 http://en.oreilly.com/railswinter10). I don't think anyone who did could possibly think that Rails is going to do anything but totally crush going forward. Rails 3 will still have opinionated defaults; it will just be easy to swap them out for other options. Most newbies will still use the default stack,* but experts (who always insist on customization) will have a much easier time than they currently do. * Readers of my Ruby on Rails Tutorial book (http://www.railstutorial.org/book http://www.railstutorial.org/book) will use RSpec instead of the default Test::Unit. Currently (with Rails 2.3.5) this requires some fiddly configuration but---thanks to the modularity the article's author disparages---RSpec will feel like a default test framework in Rails 3. For example, by configuring Rails 3 to use RSpec, commands like $ rails generate model User will automagically use RSpec instead of Test::Unit.