15 Apr '12, 10am

says “we now only reload classes from files you’ve actually changed”, but I think that's wrong.

So we didn’t quite make the December release date as we intended, but hey, why break a good tradition and start hitting release targets now! In any case, your patience has been worldly rewarded young grasshopper: Rails 3.2 is done, baked, tested, and ready to roll! I’ve been running on 3-2-stable for a few months working on Basecamp Next and it’s been a real treat. The new faster dev mode in particular is a major step up over 3.1. Do remember that this is the last intended release series that’s going to support Ruby 1.8.7. The master git branch for Rails is now targeting Rails 4.0, which will require Ruby 1.9.3 and above. So now is a great time to start the work on getting your app ready for the current version of Ruby. Let’s not hang around old versions forever and a Sunday like those Python guys :). There’s a v3.2.0 tag on Github and we of course we still have the 3-2-st...

Full article: http://weblog.rubyonrails.org/2012/1/20/rails-3-2-0-faste...

Tweets

ActiveRecord Store in Rails 3.2 is really handy!

api.rubyonrails.org 18 Apr '12, 2am

Store gives you a thin wrapper around serialize for the purpose of storing hashes in a single column. It's like a simple k...

Making the Web Fast(er) one Rails page at a time

rubyflow.com 24 Apr '12, 7pm

Making the Web Fast(er) one Rails page at a time Posted by igrigorik on April 24, 2012 — 0 comments RailsConf 2012 slides ...