Re:Rails 3.2.13 - Performance regressions and major bugs
by Axsuul on Wednesday March 20, 2013 @05:07PM
(#5410328)
Would you really be willing to give up the productivity benefits and developer happiness over a few mishaps? Also, it's generally a good idea not to upgrade to the next software version until seeing the repercussions its had.
[ Parent
| on HN ]
Re:Rails 3.2.13 - Performance regressions and major bugs
by sergiotapia on Wednesday March 20, 2013 @05:09PM
(#5410347)
That's the thing! I find myself ping-ponging in my mind between "But Ruby and ActiveRecord are so beautiful and easy to use." and "But what happens if the 'magic' breaks?"
Trust me, I have been thinking about what you say every day for the past 5 days.
Re:Rails 3.2.13 - Performance regressions and major bugs
by damoncali on Wednesday March 20, 2013 @09:45PM
(#5412216)
You're thinking too much. Unless it's a "the world is ending" level security fix like the recent yaml stuff, wait a couple weeks for this stuff to come out and get fixed. Then upgrade.