Re:Upgrading GitHub to Rails 3 with Zero Downtime
by brandonmenc on Monday September 15, 2014 @11:45PM
(#8322928)
Probably any framework is painful to be two major versions behind with.
[ Parent
| on HN ]
Re:Upgrading GitHub to Rails 3 with Zero Downtime
by davidw on Tuesday September 16, 2014 @07:52AM
(#8324009)
I'm a big fan of Rails, but I think that Rails does not really give a lot of weight to backwards compatibility. The Ruby community in general often feels like it's always charging forward, very often with tons of cool new things, but occasionally leaving broken, incompatible software in its wake.
Re:Upgrading GitHub to Rails 3 with Zero Downtime
by yazaddaruvala on Tuesday September 16, 2014 @12:28PM
(#8325333)
You seem to imply there is something wrong with that.. As long as you bump the version number and support the old version for bug fixes, it ends up being the best way to move the world forward.
Re:Upgrading GitHub to Rails 3 with Zero Downtime
by ufmace on Tuesday September 16, 2014 @03:39PM
(#8326648)
I am a fan of Rails and am doing some work on it, but it's pretty clear that while Rails is bumping version numbers cleanly, they aren't putting all that much work into supporting older versions. Github has been doing their own work backporting security patches to Rails 2.3 for years.
Re:Upgrading GitHub to Rails 3 with Zero Downtime
by davidw on Tuesday September 16, 2014 @01:52PM
(#8325878)
I tried to keep my comment kind of neutral, actually. There are advantages and disadvantages, and the Ruby community does pretty well, by and large.
Re:Upgrading GitHub to Rails 3 with Zero Downtime
by tonyedgecombe on Tuesday September 16, 2014 @04:42AM
(#8323579)
Why would it be any more difficult to migrate from 2.3 to 3 now instead of four years ago?