Yaroslav Markin

On gem Audition. Ractors are probably _the_ topic for Ruby in 2026, if we don't count the AI boom for a second. It looks like they will finally be stable in Ruby 4.1. The main battle now is Ractor-safe Rails, and some amazing engineers are on it; you can follow the weekly progress in This Week in Rails. But Rails is just a bunch of gems, and most production Rails applications rely on dozens, if not hundreds, of third-party gems. Even if you're running a Ractor-ready Rails, your gems need to be Ractor-ready too. I suspect that for most gem maintainers, ractorizing a gem looks hard enough that it's simply not worth it. And that is how the Ractor dream could end before it even begins: a Ractor-ready Rails, a handful of core gems, and that's it. That's why I'm invested in Audition. I believe the answer is a tool to analyze your code for Ractor compatibility, and, most importantly, fix most of the problems _automatically_; for everything else, give detailed instructions on what to try until the audition passes. Audition is written by AI agents, and every now and then I have it re-learn its rules from the latest ractorization work in Rails and the Ractor team's findings (the current fix knowledge base distills the 61 ractorization commits that landed on Rails main through August). If you have better recipes, please send a PR. And if you maintain a gem, try Audition on your own code. You might get your code running under Ractors on the cheap! github.com/yaroslav/audition