This was a pleasure to read. I really think this is the most intelligent solution to older rails projects. It's also an eye opening topic for all startups out

This was a pleasure to read. I really think this is the most intelligent solution to older rails projects. It's also an eye opening topic for all startups out there, including mine, that rely on rails -- you will need to fight to keep your applications and servers safe. I guess you could say I spend so much time building and breaking to achieve something, that the thought of long term support often slips my mind. Still, when building I do my best to stay away from '3-in-1' gems (aka, admin-backbone-devise-api-comments-aws) that have a 0% possibility of surviving. I stick to gems that are up there in the star count on github, and try not to touch anything that has been stagnant for 6months+. Obviously this isn't a perfect solution, but I feel a bit more confident in the survival/ longevity of the application.