Honestly I don't think that's a bad idea. Where I work I develop a web app that's written in Rails, and it's replacing a legacy PHP 5.6 app. Now here's the thi

Honestly I don't think that's a bad idea. Where I work I develop a web app that's written in Rails, and it's replacing a legacy PHP 5.6 app. Now here's the thing - no-one is using the PHP app anymore, but we do still have some old data on there that we made a decision not to port over to the new app. At the time it seemed like it wouldn't be a problem - just keep an old version of the app up for those who need to view historical information. Now I'm thinking I'll have to set aside some time to either port it to PHP 7 (which isn't really a priority) or come up with something else for viewing that historical data.