Back

@byroot I am surprised you do not see other people issue with 3.3.0. But good news with 3.4-dev

@benoit yeah the issues with 3.3.0 are really unfortunate but don't impact us, even thought part of that 4% may be attributed to their fix.

One is specific to ARM64-linux, which we don't use, the other is a leak in YJIT in case of singleton class abuses, which we fairly aggressively eliminated a while ago.

But even if we were impacted, we have the means to patch our rubies, so it wouldn't have stopped us.

I do wish 3.3.1 go out soon though, but for the community.

@lucian yes, we upgrade Rails weekly.

@byroot this is super cool that you run ruby 3.4 dev and rails main.

I am about to run a rails new this weekend and I was kinda thinking to live on the edge for Rails but your post nudges me to also try ruby dev.

@lucian Note that I don't recommend anyone to run ruby-dev versions in production.

It makes sense for us because we actively contribute to it, and have a very mature infra to ensure it works.

Now if it's a personal project, help yourself, but I'd avoid it for professional stuff.

@byroot ah yes. Thank you for the clarification.

I am starting a personal projects :) so it should be “safe” to use them :))

@lucian That's the goal yes. Too bad we don't use ARM64/Linux, we'd have caught the glaring bug in 3.3.0 before release .

Maybe next year we'll have ARM64/linux coverage.