4 ms·
My pitch: If you plan to support your app for a long time, you will realistically have to upgrade to 3.x eventually. Better to do so at the same time as everyo
by jdminhbg 16y ago
My pitch: If you plan to support your app for a long time, you will realistically have to upgrade to 3.x eventually. Better to do so at the same time as everyone else to benefit from the hivemind's concentrated power. Plus, given advances in SCM technology, branching should be easy, and you can abandon/return to your upgrade branch later if you have insurmountable problems.
- SkyMarshal 16y agoTo play the devil's advocate, maybe it's best to the let the pawn... er, early adapters, go first, find all the gotchas, blog about them, patch them, and then upgrade. ;) Disclaimer - I'll happily be one of the pawns. :D
- rbranson 16y agoAs a paw.. I mean, early adopter, I've been using Rails 3 for things-people-pay-me-for since beta3 and seen it really mature over the last few months.
- spitfire 16y agoBetter yet, be a not /quite/ so early adopter. Move over once the hive mind has sorted all the problems, but when they're still fresh in their minds. I certainly buy that you'll have to update sooner or later, but I'd rather do it on my terms.
- billmcneale 16y ago> If you plan to support your app for a long time, you will realistically have to upgrade to 3.x eventually. The keyword here is "eventually". Wait for the next point release before upgrading. Just like Windows.
- steveklabnik 16y agoIn this case, the next point release will remove all of the deprecation warnings that you're given with this release. So, if you use 3.0 now, you'll have a nice checklist of things you need to fix before 3.1. If you jump right into 3.1, stuff will break.
- riffraff 16y agoWell you dont need to upgrade to support something, i have a rails 1 app around working without issues for years, though i plan to upgrade it ;)