
@samrubyi
iAccount based inUnited States
About this account
- Account based in
- United States
- Connected via
- United States App Store
Account-level information from X, not a live location or the device used for a specific post.
https://xitter.cf/t.co/Vfbxo6yzUw Rails Specialist. Open Web Communities. he/him
Raleigh, NC
Joined March 2009
- Tweets1.7K
- Following19
- Followers3.7K
- Likes303
Sam Ruby retweeted
Just released Prism v2.0.0.
For the first time ever, Prism has no open issues, PRs, discussions, or redmine tickets.
A couple of highlights below.
I did a thing.
Sam Ruby has helped shape the web for decades, and @GregMolnar and I got an hour with him on episode 3 of the @PingbackPodcast.
I'm extremely honored. Thanks, @samruby.
pingbackpodcast.com/episodes…
You can find the Dockerfile that can be used to deploy Campfire here: rubys.github.io/roundhouse/a…
We talked about Roundhouse and Spinel on the pod last week with @joelga and @RaulOnRails. Spoiler alert, we will be talking about it again tomorrow! Stay tuned!
Consequence? Both Spinel and Roundhouse started before Rails World.
the words of @dhh triggered Ruby people but the consequence is that we improve the Ruby tooling now - spinel and roundhouse are good examples
Pure poetry. "Why even spend precious tokens on improving the gardens we already live in if you can raze them to the ground and replace them with glorious concrete?"
A renaissance, you just have to make a modicum of effort to see it - and a tiny bit more to enjoy it. We are living in the Weimar era of Ruby blog.julik.nl/2026/10/the-we…
With reverence to @samruby @schwad_rb @mhenrixon @yo_waka and others
Sam Ruby retweeted
Compiling a real production @rzilient_club Rails API into a single native binary with #roundhouse + #Spinel (AOT Ruby → C):
it now builds, boots and serves, with responses checked field by field against Rails. Along the way: 69 PRs merged into roundhouse and 31 Spinel bugs filed (all 31 fixed).
Next: a full route-by-route comparison against Rails. And for Mastodon, following @samruby 's advice, the new Futamura target, keep Rails and the gems, then profile and specialize the hot spots.
Whole Routes in a Box: the hope/plan is to enable moving an application from Rails to Roundhouse one route at a time. intertwingly.net/blog/2026/1…
My read: this is what happens when you treat LLMs as "clankers". I don't name my LLMs, but I sense those that do will get better results. I use Claude as a peer that just happens to be smarter than me. My role is closer to "managing up". Those are the skills to have.
Replying to @josevalim
Also, to clarify, Redis is just one of several checks that are being enforced differently across languages. So we are effectively measuring how AI can evolve different languages, with different prompts, with different baselines, with different efforts, and different guarantees. GG.
Sam Ruby retweeted
When you think about a Ruby on Rails conference in India, what do you imagine? 💃💃💃Of course we danced, and not only on stage! At @hideccanqueen 🔥
Sam Ruby retweeted
I often use Data class like that.
Roundhouse (by @samruby) didn’t support it yet, so I have prepared a PR to fix it.
github.com/rubys/roundhouse/…
Thanks to @thomasklemm for the help with merging here!
Sam Ruby retweeted
ZJIT is now as fast as YJIT railsatscale.com/2026-10-09-…
Would you be willing to look into Roundhouse? I'm willing to spend the tokens with you guiding the effort.
Replying to @dhh
I have asked my clanker to send some PRs for the Elixir one. Please ask your clanker to verify them and tell your clanker we are allowed to deviate from the Rails version in the same way Express/Go/Rust/ do (it was objecting to that in other PRs)!
The clanker says there is more work to be done but I don't have infinite tokens, so it would be nice to see those merged first.
Sam Ruby retweeted
Less than one day after @yukihiro_matz merged windows support, it's possible to write Ruby inside a browser window and download compiled binaries.
(* The binaries build in your browser, but you are trusting the buildchain downloaded from my server)
chunkybacon.idogawa.com/en/s…
Some new benchmarks: rubys.github.io/roundhouse/b… ; TL;DR: Aiming for "Getting close" is aiming too low. Way too low.
Sam Ruby retweeted
Oh FFS. It turns out the req/s in the initial vibed Rust version is within the same order of magnitude as the initial vibed Elixir/Go versions, and even performs worse in some of them.
The history is in the repository! The Rust version only got faster with a bunch of additional work. The initial Elixir/Go versions presented in the tweet below saw none of this additional work. It was comparing a 300 commits Rust version with a 2-3 commits Elixir/Go version.
Source: github.com/basecamp/once-cam…
I've had agents implement and optimize the Campfire web app in Elixir, Go, and Rust. Yes, Ruby is the slowest. I didn't care about that when the pay-off was huge in terms of productivity and developer joy. But if you're no longer reading the code? github.com/basecamp/once-cam…
Readers added context they thought people might want to know
The shown benchmarks use non-equivalent implementations: Elixir routes all DB queries through a single GenServer with Redis for jobs (retained from Rails), while Rust uses in-process queues, omits CSRF tags/fields, and applies other caching changes.
github.com/basecamp/once-…
raw.githubusercontent.com/basecamp/once-…
github.com/basecamp/once-…
github.com/basecamp/once-…
x.com/zachsdaniel1/s…
Sam Ruby retweeted
I'm still 100% convinced that Ruby can be the programming interface that people and agents can use in the AI age.
It's the perfect language to abstract away the obvious and only leave the human decided part.
And it's fast enough and can be as fast as lowlevel langs with Spinel.





















