My first version of this story was: “DHH killed Rails at RailsConf.” Both halves were wrong.
RailsConf held its last edition in 2025. What actually happened was the opening keynote of Rails World 2026, the Rails Foundation’s conference, on September 23 in Austin. And DHH didn’t kill Rails. What he did was more uncomfortable: standing in front of a room full of people who make their living with Rails, he said he no longer needs it for one of his flagship products.
The fact that I latched onto the short version says something about how this kind of news reaches us. Someone sums it up in a sentence, the sentence spreads, and two days later we all have strong opinions about an hour-long talk that almost nobody watched in full.
#.What he said
The core of the talk is a decision 37signals made a couple of weeks ago: stop writing code by hand. “Pencils down,” he called it. Writing code by hand at 37signals is now an exceptional state, he said, “like seeing a bug in Sentry”: a sign that something in the machine went wrong and needs fixing. He said he had retired from being a professional programmer, around March. And he predicted that writing code by hand is no longer an economically productive enterprise for the vast majority of programmers at the vast majority of companies, and that by the end of the year that will extend to “virtually all domains, virtually all programmers, virtually all companies.”
Then came the part that hurt. HEY, 37signals’ email service, is being rebuilt as native applications on the frontend and Rust on the backend. No Rails on either side. DHH spent a good while explaining how much he dislikes reading Rust, and chose it anyway, because he has no intention of reading it: he says he doesn’t know any Rust, considers that a feature, and evaluates what the agents produce as a black box, from the outside, like any business owner who ever commissioned software from a team.
And he closed with this, verbatim:
“So take the white pill. Take the optimism pill. Lean in, even with the uncertainty, even with the stress, even with all of it, realize there is only one choice. And that is for you to embrace the future with optimism, with gusto, with full acceleration. The black pill is for fucking losers. Don’t be a loser.”
What he didn’t say is that Rails is dead. heise is explicit about that, and in the talk itself DHH says the web is still wonderful for services people use in passing, without installing anything, and that Rails is particularly well positioned to stay in play there. In his view, convention over configuration leads directly to token efficiency, and the one-person framework fits what the age of agents demands.
#.Why it sounded like a funeral
A YouTube comment, picked up by Global Nerdy, put it as “the most confusing funeral I’ve ever experienced.” Jared Norman explains it well in What About Rails?: DHH moved a flagship app off Rails at a conference that bears its name, and the one moment he spoke directly to Rails developers, he said nothing about where the framework is headed. If you built your career on Rails and flew to Austin to hear what comes next, that sounds like a goodbye, even if it isn’t one.
#.Before listening
I’ve worked with Rails, and back in 2019 I quoted a DHH tweet right here about controllers to defend a way of organizing code I still use. That predisposes me to defend him. At the same time, the tone of this talk makes me uncomfortable, and it’s very easy to let that discomfort decide for me. Both are ego, pulling in opposite directions.
And there’s another reason many people no longer listen to him. A year ago, in As I remember London, DHH wrote that “native Brits” had gone from more than sixty percent of London to about a third, and described the flags at Tommy Robinson’s march as “heartwarming.” Robinson is a figure of the British far right. That post drew a strong backlash across much of the community. Listening to his technical argument doesn’t oblige me to agree with him on that, or to pretend it doesn’t exist. You can take an idea seriously without adopting the whole person.
#.Why he’s worth hearing out
Strip away the tone, and what’s left is an unusual amount of transparency.
DHH could have rebuilt HEY quietly and mentioned it in a blog post months later. Instead, he said it at his own framework’s conference, in front of the people with the most to lose by hearing it. You can read that as showmanship too: DHH has always known how to use a stage. But showmanship doesn’t explain everything he shared, because a good part of it doesn’t flatter him.
He told us what didn’t work. In the spring, to finish Basecamp 5, they let several designers build the final features with agents. Each PR looked reasonable on its own; together, twenty or thirty of them left the architecture looking like Swiss cheese. They went back to reviewing everything by hand. He now says that was the wrong conclusion, because he believes the models that arrived shortly after would have made it work. You can argue with his reading, but not with the fact that he showed the mistake.
He acknowledged the unease from the first minute. He said this moment is exciting and also a little unnerving, because any prediction is out of date twenty minutes later. To explain it, he talked about the portrait painters whose craft was changed by photography, and showed one of them: Laurits Tuxen, his great-great-grandfather. He asked us to look at the era that’s ending not with regret, but with joy for what it was. You can disagree with his conclusion, but he put himself inside the story he was telling.
And his actions back his words. One of the most critical comments on Hacker News said that if he thought Rails was better, he would have used it: actions over words. Fair, but it cuts both ways. His actions say the bet is real, not just a pose.
What he leaves on the table is a question you can’t wave away with a one-liner: if writing code by hand stops being the center of the job, which part of it is still ours?
#.What I’m not taking with me
There are three things from this talk I’m leaving behind.
The first is “there is only one choice.” Near the end, DHH says no one knows anything about the future, so the rational choice is to be optimistic. But in the same talk he had predicted that by the end of the year virtually all programmers, in all domains, would stop writing code by hand. It’s hard to hold both at once. And calling anyone who hesitates a loser isn’t optimism: it’s ending the conversation.
The second is the numbers. He said he wrote about 150,000 lines of code in August, against roughly 30,000 a year for two decades. Credit where it’s due: he hedged it himself, calling lines of code “a weird, fuzzy, malleable” measure and noting that much of that volume is Rust he never looks at. Still, back in April I wrote about the death of LOC, and measuring productivity in the age of agents in lines of code still strikes me as the wrong yardstick.
The third is where you’re standing when you say it. In the talk, DHH describes all this capability as available “for a small price and a subscription.” Claude’s Max plan, for example, starts at $100 a month. In the same Hacker News thread, someone wrote that “hundreds of dollars” a month is most of their salary. From Panama, that’s not a footnote. “Pencils down” is easier to say when the cost of the tools doesn’t weigh on your budget.
#.Hear the whole thing
Rails isn’t going away tomorrow; an enormous amount of software depends on it. What unsettles me about this story is something else: how quickly we want to turn an hour-long talk into a one-liner we can be for or against, and how easy it was for me to repeat the short version.
So my recommendation is simple: watch the keynote before forming an opinion, and then read the people who answered it with arguments. Sam Ruby, a long-standing figure in the community, makes the case that Rails is precisely the high-level notation that serves an agent best: it fits entirely in its context, says each thing once, and the models already know it. If he’s right, the question of which part of the work is still ours has a less dramatic answer than “pencils down”: choose the notation well, and verify what gets written in it.