3 ms·
Is Rails still (I have not used it since 2016) incredibly hard to migrate after a couple of years? I have java/spring, asp.net (core) and php (no framework) in
by tluyben2 6y ago
Is Rails still (I have not used it since 2016) incredibly hard to migrate after a couple of years? I have java/spring, asp.net (core) and php (no framework) in production and I can upgrade after a decade not touching and everything still works. I had Rails upgrades after 1-2 years that were absolute nightmares. I'm not sure about other people here but I really don't want to suffer through that 'for fun' while I don't have to. Speed of developing is not so much faster that I would take this for granted. But maybe things changed.
Edit; it was a question, what's with the downvotes? It used to be bad; I'm not the only one saying that. It's normal (Laravel, Node etc have it as well; it's fast moving).
- Ecco 6y agoI don’t get why you’re being downvoted. You’re right, a while ago that was a major headache. The good news is that it’s now much better! - Bundler makes keeping track of gems trivial - Rails defaults are explicitly version-bound. E.g. you can update to Rails 6 and keep using Rails 5 defaults. - There are now extensive official guides on how to update.
- tluyben2 6y agoGood to hear, thanks! Maybe i'll try it again as it was quite nice outside updating/upgrading.
- bdcravens 6y agoThe upgrades prior to 2016 were definitely painful, especially 3.2 -> 4.0. In recent years, there's been less changing the underlying framework; new versions tend to just add new features.