News for hackers. Stuff that matters.
Re:The Costs of Keeping Your Rails App Up to Date, Or Not by bdcravens on Monday January 27, 2014 @11:13AM (#7131067)
I can’t even guess how much time I’ve saved by using Arel, CoffeeScript, SASS, and the Asset Pipeline

I don't think that we've seen these types of "innovations" in 4.0 or 4.1 beta. (not saying they're not valuable, only addressing developer productivity discussion) Also, you have to subtract learning curve from time saved - over time, it's a net win, but not immediately.

By keeping your application up to date, you ensure that you’ll have a larger pool of developers who can maintenance your application.

Isn't there a period of time where this isn't true? For a while, you'll reduce the pool of available developers, as not everyone gets up to speed right away on the latest version.

Re:The Costs of Keeping Your Rails App Up to Date, Or Not by Robin_Message on Monday January 27, 2014 @12:12PM (#7131539)
Most decent developers will want the opportunity to work on the latest version. Certainly keeping reasonably current is much lower risk than not upgrading.
Re:The Costs of Keeping Your Rails App Up to Date, Or Not by bdcravens on Monday January 27, 2014 @01:02PM (#7131893)
Wanting to work on, and being qualified to work on, are 2 different things. I'll agree that keeping reasonably current is best. To that end, I think there's a sweet spot - probably 6-12 months after a minor or major version upgrade.