Sent from my iPhone
On Jul 3, 2010, at 11:52 AM, Fernando Perez <[email protected]> wrote: >> Good luck, >> >> -Conrad > > Hi Conrad, thanks for the tip. Yeah I'm eagerly waiting for Rails 3 to > get released! > > In the mean time I managed to make Rails 2.3.8 play nicely with Ruby > 1.9.1 and that's very painful to do. I would suggest people to stick to > Ruby 1.8 for some time until everything gets settled. 3rd party gems > also have to be updated to be compatible with the new 1.9 encoding > handling. Many gems have been updated to support Ruby 1.9 and it should be super simple to fix the ones that are not compatible. I had a very large code base using a lot of gems and plugins. The ones that had associated tests were much easier to fix in general. Lastly, getting up to speed with the syntax and semantic changed made porting for me the easiest as I worked through the various issues. In short, you'll have to make changes to your code either now or later. Thus, I prefer to make incremental improvements over. For example, moving to Ruby 1.9.2. Next, I plan to move to Rails 3. I go in knowing that somethings will not work and will need to be fixed which is a part of software engineering. Just create another branch and just do it. :-) Good luck, -Conrad > -- > Posted via http://www.ruby-forum.com/. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
