Rails World 2026: DHH retires from hand-written code and moves Hey to LLM-generated Rust

A retirement and a bet on English

At the opening keynote of Rails World 2026, Ruby on Rails creator David Heinemeier Hansson announced that he has retired from professional programming and now describes himself as a "maker", according to Jared Norman, a developer who builds applications with Rails and wrote a detailed critique of the talk on his blog. Norman's central complaint is that the keynote of the world's premier Rails conference had very little to do with Rails.

Among the claims Norman reports from the stage: English is now the best programming language because of large language models, people do not necessarily need to read the code those models produce, and reading code at all should become the exception rather than the rule — comparable to stumbling on a bug in Sentry. Hansson also said that writing code by hand is no longer economically productive for most programmers at most companies, and that by the end of the year this would extend to nearly every domain, programmer and company.

Hey rebuilt as native apps on a Rust backend

The concrete announcement was about 37signals' email service Hey. According to Norman, the next version is being built as native applications for every supported platform, with the server side written in Rust and generated largely by LLMs. Norman notes this reverses positions Hansson held for years on both native apps and Rust; Hansson reportedly still considers Rust unpleasant for humans but well suited to LLM generation, and since he is not reading the output, he now values its performance and stability.

Hansson cited personal numbers in the talk: roughly 150,000 lines of code produced in August 2026, versus an average of about 30,000 lines per year before LLMs — much of the recent output admittedly verbose Rust. Ruby, which made up about half of his work over the past two decades, accounted for only 3% of what he wrote this year. He also called for every service to expose a CLI so that agents can interact with it without a graphical interface.

The Rails-specific content, per Norman, amounted to the framework remaining a good fit for web applications like Basecamp and being well suited to AI-assisted building, with convention over configuration recast as "token efficiency", plus a citation of Evil Martians' agent evals showing that AI tools handle Rails well.

Norman's critique: reassurance instead of a plan

Norman argues the keynote effectively announced that a flagship Rails application is leaving Rails. In his reading, the long-running pitch that small teams could build ambitious products with Rails has narrowed: Rails was a workaround for a bottleneck that LLMs have now removed, and the framework is left as a solid choice for projects that must run in the browser. He also finds the CLI demand inconsistent, since 37signals differentiates its products through opinionated UI and UX — enough to justify rewriting Hey as six native apps — while simultaneously suggesting interfaces matter less if agents drive everything through terminals.

He is skeptical of the numbers too. Hansson reportedly conceded that lines of code is a poor metric and hard to compare across languages, then compared 150,000 lines of machine-generated Rust against his historical hand-written Ruby anyway, while admitting he tolerates generated Rust he would never accept in his own Ruby. The backend claims for the Hey rewrite — 99% less CPU, 95% less memory, and ten hosts needed only for redundancy — face a similar apples-to-oranges problem when comparing Ruby with Rust.

On governance, Norman points out that much of Rails' day-to-day maintenance comes from Shopify and others, but Hansson historically set the vision. He notes that the Mosscap fork argues Rails is essentially finished, that Hanami offers an actual roadmap for Ruby web development, and that the keynote's closing pep talk — telling Rails developers they are the best of the best, in a Top Gun register — could have been delivered word for word to Django, Laravel or Spring Boot developers.

Why it matters

Rails runs a large share of production web applications, and its ecosystem looks to this keynote each year for direction. Instead, the framework's creator said his own Ruby output has fallen to 3% and predicted hand-written code will be obsolete for almost everyone within months. For teams investing in Rails, the open question is whether the framework's future is deliberate growth or quiet maintenance — and, if Hansson has moved on, who supplies the vision. Norman's post frames the keynote as flattery without a plan, and that gap, more than the AI predictions themselves, is what the Rails community now has to reckon with.