2 ms·
This problem isn't specific to Rails 3.1. At some point, your frameworks need to be upgraded, because at some point the developers stop supporting your version.
by borkborkbork 10y ago
This problem isn't specific to Rails 3.1. At some point, your frameworks need to be upgraded, because at some point the developers stop supporting your version. Django announced recently that 1.7 would no longer be getting security fixes. The question is: how much will it cost to upgrade when the day comes? Frameworks and communities that encourage less magic and less dependencies will always be less costly to maintain.
- engineerDave 10y agotrue but even staying current across small SemVer changes can be a relatively large burden
- borkborkbork 10y agoAgreed