why forked ten_year_rails ? what's the difference? about next_rails HOT 2 CLOSED

@silva96 Good question. A couple of years ago we were trying to make contributions to ten_year_rails but we weren't making any progress with them. It seemed that the company had decided to archive the repository. That is why we decided to start next_rails.

At FastRuby.io | Rails Upgrade Services we work with very old Rails applications and ten_years_rails has a dependency on actionview which makes it difficult to use it with really old versions... so we decided to get rid of that. I think that is the main difference when it comes to the codebase: clio/ten_years_rails@master...fastruby:master

There were more differences between the gems in the past. At some point the team at Clio decided to merge the PRs that we had submitted to the project.

I hope this answers your question.

I think it is a good idea to add a note to the README. 👍

from next_rails.

Thanks, i'll close this issue

from next_rails.