"We’ll be making sure we get performance of Active Record back to at least 2.3 levels before release." Why call it a Release Candidate if you still plan on tweak more stuff?
For new RoR programmers, is it recommended to just start in with Rails 3, or stick with Rails 2 until Rails 3 "stabilizes"? There are a bunch of Rails 3 books out there; do they generally line up well with this release candidate, or are they full of old information that a new RoR programmer would stumble upon and not understand how to fix?<p>[EDIT] The three books I saw available that specifically mention Rails 3 in the title are available for pre-order, so hopefully they will be pretty up-to-date.
I haven't had a look at 3.0 yet. What's the effort like to upgrade? I have this suspicion that it's basically going to be a major rewrite for most of my projects with all the new apis and deprecation. It's almost as if it were a completely separate project that offered some degree of Rails compatibility to help people transition. <i>However</i>, that's the impression I get from reading things - how is it in practice for those who have updated significant code bases?