4 ms·
Every year-end, I update my Rails app. Lately, it's been stable, and the updates just improve performance, so it's gotten easier.
by tan-z-tan 2y ago
Every year-end, I update my Rails app. Lately, it's been stable, and the updates just improve performance, so it's gotten easier.
- tbolt 2y agoI haven’t worked in ruby or rails in a few years but both seem like they’re in great spots and I’ll be spinning up a new project with Rails 8 soon. Hype
- tan-z-tan 2y agoSounds good. Rails is still my first choice for personal development (though I've been using Next.js more often recently).
- Gigachad 2y agoI started at a company 3 years ago that was on Rails 5.1. After 3 years on and off work I've managed to get it to Rails 6.1. The process is such an incredible nightmare on a large app. Currently stuck on trying to get Ruby 3 working.
- prh8 2y agoSame thing for me—4 years ago, Rails 4.2. Now on 6.0, work for 6.1 is wrapped up. I did just finish going from Ruby 2.7 to 3.3. Any particular issues you’re having, or just working through the process?
- Gigachad 2y agoDon’t have the exact details on me but it was just the change for the method params hash thing. The stack trace seems to be pointing places that aren’t the source of the issue, just where it got triggered in some dynamic way. Probably just need to spend more time understanding exactly what changed and how to convert stuff.
- ljm 2y agoAt some point you just have to rip the bandaid off and put any ongoing work on pause until the upgrade is done. Otherwise it'll be another 3 years on and off while you try to do the upgrade but the codebase keeps changing underneath you. And if that isn't happening and there's no other development on the codebase, why bother upgrading it?
- lifesaverluke 2y agoCurious what specifically you’re running into?