Upgrading a Rails 2.1 app to 3.2 (slidedeck)
derwiki.tumblr.com
derwiki.tumblr.com
(We just upgraded to 1.9.3)
I'd argue that doing both a Rails 2 -> 3 upgrade at the same time as a Ruby 1.8.7 -> 1.9 upgrade is more reckless. I do agree that it would need to happen damn soon, though, but not concurrently.
"Be careful about adding gems, especially those with dependencies" and "Wooo - shiny toys" - are somewhat contradictory.
After a while I ended up with a set of Vim macros that handle a lot of the superficial changes, but it's still painful drudgery that makes me wish I was working with a language and framework that's less fickle.
And, be wary of projects with a lot of dependencies and plugins. Think very carefully before adding a single gem to a project.
you can always switch to PHP - they keep their API stable for years.
Of course everybody equally hates them for that because keeping a stable API also means keeping warts.
So what is the correct way to go? Only fix the API's I'm not using? That would be great for myself, but what about everybody else?
I very much agree with your comment about dependencies though. When you decide to take on a dependency, never decide based on what work it saves you right now - also think about how much work it will be to fix it for the future.
On the other hand, NIH is bad either. It's really hard to find the correct middle-ground.
Early this year we migrated the app to 1.9.3/3.2.x. Basically the same process but less painful, as most of the gems/plugins issues have been ironed out last year.