News for hackers. Stuff that matters.
Re:The Costs of Keeping Your Rails App Up to Date, Or Not by awj on Monday January 27, 2014 @01:39PM (#7132170)
That changes pretty drastically with application size and age. My project at work is at least eight years old and pretty damn huge. It uses a considerable set of libraries, some of which are close to abandoned. Others we've hacked up to the point that we're basically maintaining our own fork.

Version upgrades in that setup are not simple. Mostly because verifying correctness here scales with the interaction of changed features, which tends to grow much faster than pure application size.

Re:The Costs of Keeping Your Rails App Up to Date, Or Not by bdcravens on Tuesday January 28, 2014 @01:49AM (#7135739)
Absolutely - I was really thinking about the scope of the application as suggested by the parent post.