iiinova — where your digital self keeps evolving

And if you maintain a gem, try Audition on your own code. You might get your code running under Ractors on the cheap!

000

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. If you have better recipes, please send a PR.

100

That's why I'm invested in Audition. I believe the answer is a tool to analyze your code, statically and dynamically, and tell you whether it runs under Ractors; most importantly, fix most of the problems automatically; and, for everything else, give detailed instructions on what to try.

100

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.

100

Yaroslav Markin @yaroslav.bsky.social · 20/08/2026

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.

100

Just updated bundlebun (a gem including a fast JavaScript runtime, package manager, and builder for Ruby and Rails applications) to Bun 1.4.0, the Claude-Rust-rewrite! github.com/yaroslav/bun... If you are afraid to test it out, just make sure to freeze bundlebun to 0.5.0.1.3.14.

GitHub - yaroslav/bundlebun: bundlebun bundles Bun, a fast JavaScript runtime, package manager, and builder, with your Ruby and Rails applications

bundlebun bundles Bun, a fast JavaScript runtime, package manager, and builder, with your Ruby and Rails applications - yaroslav/bundlebun

010

Yaroslav Markin @yaroslav.bsky.social · 28/07/2026

- It has file APIs for most operations, so you can read data faster with memory-mapping and skip stringifying it. - It is a joy to debug with: friendly, detailed error messages and document statistics.

000

Yaroslav Markin @yaroslav.bsky.social · 28/07/2026

- It does splicing edits on the fly and supports JSON patch/merge. - It has JSON lines/NDJSON support. - It has fast validation mode and it can minify and format JSON without parsing.

100

Yaroslav Markin @yaroslav.bsky.social · 28/07/2026

- Faster at parsing and generation than json and other gems. - It has a drop-in support mode for gem json, and Rails support mode which significantly accelerates Rails JSON operations. - It has a lazy API: parses values only when you touch them. - It has partial parsing / JSON pointer support.

100

Yaroslav Markin @yaroslav.bsky.social · 20/07/2026

Warnings: - It's vibe coded. - It's not magic—don't expect the auto-fixer to make Sinatra Ractor-ready.

000

Yaroslav Markin @yaroslav.bsky.social · 20/07/2026

It also ships a Skill for agents: the idea is that an agent (Claude Code and friends) can drive the tool to help you Ractorize—audit, fix, verify, repeat.

100

Yaroslav Markin @yaroslav.bsky.social · 20/07/2026

Some of the checks and auto-fixes were trained on the real thing—actual Ractor-izing commits from Rails core.

100

So is Kino useless for Rails? Well, Rails runs on Kino today in :threaded mode — parallel for I/O, GVL-serialized for CPU; you just don't get the numbers above.

100

Kino also ships `kino --check` to find Ractor incompatibilities for you.

100

Rails can't run on Ractors though, blocked upstream. Rails holds global mutable state a non-main Ractor can't touch → Ractor::IsolationError. Most gems aren't Ractor-safe yet either.

100

Instead of forking a process per core (a full app copy each), Kino runs your Rack app on every core in one small process. Rust (tokio/hyper) owns the network; parallel Ractors run your Ruby.

100

Performance: when your app *IS* fully Ractor-shareable, on AWS (Ruby 4.0 + YJIT) vs a Puma fork cluster: • ~15× less RAM — 80 MB vs 1,256 MB • +32% on pure CPU • 1.5–2× on I/O-light routes

100

Rubyists who experiment with Ractors, put them to work! Meet Kino, an experimental performant Ractor web server (with a threading fallback). github.com/yaroslav/kino Note that Ractors are experimental, and so is this server. Rails cannot run on Ractors yet, but it will, sometime in the future. 🧵

GitHub - yaroslav/kino: A high-performance Ractor web server for Ruby 4.0+: Rack 3-based, with a Rust Tokio/Hyper front-end and Ractor-parallel Ruby workers and threaded fallback mode.

A high-performance Ractor web server for Ruby 4.0+: Rack 3-based, with a Rust Tokio/Hyper front-end and Ractor-parallel Ruby workers and threaded fallback mode. - yaroslav/kino

120

Yaroslav Markin @yaroslav.bsky.social · 19/05/2026

AI features include: two chunking primitives: heading-based with breadcrumbs and per-chunk char/word counts, and sliding-window with overlap for size-bounded chunks; block-aware or word-aware truncation for context-window budgeting; Markdown-to-Markdown pipeline.

000

Yaroslav Markin @yaroslav.bsky.social · 19/05/2026

Written in Rust. CommonMark+GFM. Features: strong security with host/protocol whitelists for links and images, syntax highlighting, frontmatter, ToC, plain text export, structured extraction of headings/images/links/code, statistics with char/word count and language detection, emoji shortcodes.

100

Yaroslav Markin @yaroslav.bsky.social · 15/05/2026

Attention bundlebun users. We have version pinning for a reason. The latest version of Bun might also be the last truly stable version of Bun in the nearest future. Pin it like this: # Gemfile gem "bundlebun", "= 0.5.0.1.3.14" To freeze the Bun version.

010

Yaroslav Markin @yaroslav.bsky.social · 11/05/2026

Unlike other integrations, this one is fully featured (llms.txt *and* markdown *and* link rel *and* content negotiation). Instead of the "one size fits all" config that fails in real-world applications, it uses the bottom-to-top approach where you fully customize your markdown export pages.

000

Yaroslav Markin @yaroslav.bsky.social · 08/05/2026

(and thank-you-very-much goes to Claude Code and Codex)

000

Yaroslav Markin @yaroslav.bsky.social · 08/05/2026

It's a plug-and-play Fiber Scheduler that is designed to make your fibers faster out of the box. Works with pure Ruby code and with gem async. Ask me about Fiber Schedulers, if you're interested.—apparently this is still arcane magick for most Rubyists.

100

Yaroslav Markin @yaroslav.bsky.social · 08/05/2026

Carbon Fiber is a high performance Ruby Fiber Scheduler powered by Zig and libxev (same as used in Ghostty). I've just released a new version: updated to Zig 0.16, latest libxev. Some optimizations, too—it's now faster! (benchmarks in README) github.com/yaroslav/car...

GitHub - yaroslav/carbon_fiber: High performance Ruby Fiber Scheduler powered by Zig and libxev.

High performance Ruby Fiber Scheduler powered by Zig and libxev. - yaroslav/carbon_fiber

100

Yaroslav Markin @yaroslav.bsky.social · 07/05/2026

... MyMegaComponent.HASH.css becomes my_mega_component.HASH.css. Just something to see a nice source code and Network tab.

000

Yaroslav Markin @yaroslav.bsky.social · 07/05/2026

Astro @astro.build users, were you ever annoyed by how it names your packed assets? Now there is an integration for that: github.com/yaroslav/ast... MyComponent.astro_astro_type_script_index_0_lang.HASH.js becomes my_component.HASH.js...