The Mighty Nice March To Ruby On Rails 3 And Ruby 1.9.2


Ruby On Rails 3

I’ve been working with Ruby On Rails 2.2.2 and Ruby 1.8.7 for a little over a year now. The Mightyvites site is built on that foundation, as is the Mighty Nice site, and a few of our client sites. However, with the release of Rails 3, and it’s compatibility with Ruby 1.9.2, I’m itching to upgrade both. There are a few reasons why I want to upgrade the cores of our RoR sites:

  • I don’t like to fall behind in upgrades. If you skip too many stable releases of a critical software package you’ll run into big headaches when you do decide to upgrade.
  • It’s a good excuse to upgrade everything our sites run on: gems, plugins, JavaScript libraries, etc. Just do a full upgrade release and get it over with.
  • I want core support of Rails Engines. Currently I use Rails Engines as a plugin. The less plugins to manage the better.
  • I want to drop use of the Jrails plugin and harness unobtrusive JavaScript
  • I want the bug fixes and performance improvements. I have no complaints with Ruby/Rails performance, but I would like to use the new Ruby interpreter which is supposedly 15% faster than the old (but slower than the previous interpreter with ActiveRecord? Yikes!).
  • Rails routes have a new sugary syntax (er. DSL) which will help clean up my routes.rb files.
  • Ruby has some cool new features

That’s more than enough reasons to upgrade, and thankfully I’ve got the time to do it now. In preparation I’ve cut a new development branch and I’ve talked to some fellow Chicago Rubyists to get their take on the upgrade process. One fella I met at last month’s software craftsman meetup pointed me to the rails_upgrade plugin, which I’ve already tried out and am impressed with. The plugin takes the pain out of the upgrade guess process by running through your code and printing out all you need to change and why. That’s super handy, and should help cut down significantly on the brute force break/fix upgrade cycle. There is also a good lookin’ PDF written on the upgrade process.

One thing to note: a few people have told me that moving to Rails 3 isn’t bad, but moving to Ruby 1.9 is not as easy. The reason being that many gems and plugins aren’t yet compatible. I’m going to give the move to Ruby 1.9 a try, but we’ll see how far I get.

Incoming search terms:

  • rails 3 slower than rails 2
  • Mighty Rails
  • rails 3 ruby 1 9 performance
  • rails3 ruby 1 9 performance
  • rails3 slower
  • rails3 slower than rails2
  • ruby 1 9 2 performance
  • invitation plugin in ruby on rails 3
  • ruby on rails 3
  • upgrade rails 3 to 1 9 2

One Response to “The Mighty Nice March To Ruby On Rails 3 And Ruby 1.9.2”

  1. I don’t think it’s entirely true that moving to Rails 3 isn’t bad. There’re quite a few errors I ran in to my self that weren’t too easy to track down. I actually wrote a blog post about moving to rails 3 from Rails 2. It’s not really a constructive Blog post, but more a couple notes I put out there. You may find it http://spicedcocoa.wordpress.com/2010/10/06/rails-2-x-to-rails-3/ there and I hope it will be of any use to you in your “epic journey” to upgrading to Rails 3 :-)

Leave a Reply