3 ms·
I moved us up from 2.4 to 2.7 last year trivially. Basically just changing the version base in our dockerfile. A few gems had to go up too, to support the kwarg
by cschneid 3y ago
I moved us up from 2.4 to 2.7 last year trivially. Basically just changing the version base in our dockerfile. A few gems had to go up too, to support the kwargs changes. But like... 1 day of work.
I'm looking to go to 3.x soon too, after I get our EOL'd rails & lots of gems updated.
What features in particular are you looking at in Ruby 3.0? The type system stuff seems really cool, but I haven't been hearing much about it in the wild.
- rst 3y agoUnfortunately, the switch from 2.7 to 3.0 is likely to be more troublesome, due mostly to the change in handling keyword arguments (they're no longer treated as equivalent to a last positional argument that happens to be a hash, and you need to toss in '*' to convert from one convention to the other). This isn't hard to clean up if you have good test coverage... but one reason for not having done upgrades is not having that.
- web3-is-a-scam 3y agoThis is a convention we've already adopted but we haven't had the chance to do a clean sweep of the rest of the codebase unfortunately. You're right though, it's one of our biggest hurdles to upgrading.