@tvytlx: The father of Rails, DHH, had an agent rewrite his company's chat software Campfire once each in Elixir, Go, and Rust. …
Summary
DHH had AI agents rewrite Basecamp's Campfire chat app in Elixir, Go, and Rust, showing nearly 150x performance gaps versus Ruby, and argued that AI agents writing code may shift language choice from developer ergonomics to runtime efficiency.
View Cached Full Text
Cached at: 10/05/26, 03:22 AM
The father of Rails, DHH, had an agent rewrite his company’s chat software Campfire once each in Elixir, Go, and Rust.
For the same room page, requests per second it can handle:
Ruby 244
Elixir 722
Go 3860
Rust 36260
That’s a difference of nearly 150 times.
This guy’s been saying the same thing for years:
Ruby is slow, but it’s fast to write and fun to write, and programmers’ time is more expensive than servers.
Rails was built entirely on that equation.
Then he added:
“But what if you’re not reading code anymore?”
That line made me pause for a second.
Ruby’s elegance takes care of people.
People need to read it, modify it, write it happily.
If agents take over writing code and verifying code, the benefits on the human side shrink, while the costs on the machine side don’t drop a bit.
I think the criteria for choosing a language will slowly shift from “which one’s comfortable to write” to “which one’s cheaper to run.”
Of course, don’t take this set of numbers too seriously.
He himself said speed isn’t the only factor—Rust’s slow compilation is a real hassle.
Someone in the comments said the 10x gap between Go and Rust is abnormal, probably because a few versions weren’t tuned to the same level.
For write operations like sending messages, the gap between Ruby and Rust narrows to about 27x.
But the direction is pretty clear.
The “a bit slower but people are happy” equation assumes people have to live in the code every day.
That assumption is starting to wobble.
The folks who got scared off by the Rust compiler back in the day can finally say with a straight face they don’t have to learn it anymore.
After all, the agent’s taking the scolding for me.
DHH (@dhh): 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?
Similar Articles
I'm sorry, but you still have to think
一篇评论文章分析了 DHH 让 AI 代理将 Campfire 从 Rails 重写为 Rust/Elixir/Go 的结果,指出在未人工审阅代码的情况下,重写引入了大量隐含的架构决策与性能问题(如阻塞式数据库操作、锁的误用),说明目前仍不能完全放弃阅读代码和思考。
@alphabatcher: 540,000 lines of Rails is a brutal way to learn the agent era Garry's List shipped with: > 262,000 lines of app code > …
A critique of large Rails codebases in the AI agent era, proposing a shift to skill-based development with agents, markdown skills, and TypeScript for deterministic I/O.
@github: Just one engineer and a team of agents ported the GitHub Copilot agent runtime to Rust, shipping 800,000 lines of produ…
GitHub migrated its Copilot agent runtime from TypeScript to Rust using AI agents, completing 800,000 lines of code in months with significant performance improvements.
AI Dashboard + Infrastructure + Rocket.Chat
The author shares their experience building an AI agent infrastructure using Rocket.Chat, CLI agents, and tmux, scaling to 250 clients to help them build websites. They pivoted from selling a service to teaching clients to use agents themselves, emphasizing the importance of context management in such systems.
What About Rails?
David Heinemeier Hansson announced at Rails World 2026 that he is moving away from Rails for new projects, embracing LLMs and Rust for development, sparking debate in the Rails community.