I sat front row for David's talk yesterday morning. Having talked with him the day before, I’ll admit… I wasn’t particularly surprised (nor unprepared).

A bit of a field report from #RailsWorld: the vibe here is far from doom and gloom. Quite the contrary. Wherever our industry is headed, most of us are still employed as menders… tending to systems that customers rely on and businesses are quite happy to keep paying for.

Most of us aren’t waking up to a blank canvas and designing the architecture of the future. We’re inheriting decisions made years ago, updating old patterns, working around constraints, and keeping this shit running reliably.

I think these newer tools give us an opportunity to wonder a little more about the systems we’ve inherited. To unpack why things work the way they do. To tinker with assumptions we haven’t had the time, confidence, or permission to revisit… and share what we learn so the next person, or agent, has an easier time.

That deployment model we picked eight years ago? Worth another look. Some of our web apps probably wish they were native apps. And there are plenty of architectural decisions we’ve been living with mostly because… well, we’ve been busy living with them.

There’s plenty of understandable anxiety about what these tools mean for our work. I’m increasingly curious about what they give us permission to revisit.

Once my keynote is published, I’ll share more about a little programming-language-adjacent framework I’ve been working on for approaching exactly this kind of curiosity.

In the meantime… keep showing up. Keep wondering.

Long live Ruby. Long live Rails.

p(bloom)

Concerns with his politics aside, I do think there's a truth to what he's talking about here, and that he is just spelling out the reality that developers are, or shortly will be, facing. For many this will be deeply uncomfortable to hear.

It is notable that his perspective in this talk is very much from a developer-user side rather than someone who is responsible for the framework itself. That surprises me, and I suspect it is not a good omen for Rails.

For all of this embrace of agentic development, there is nothing here on how they are adapting the framework for this new agentic development reality. Agents do currently work well with Rails, but there's nothing here pushing things forward as best as I can see.

I know for my own projects I've largely moved to Elixir/Phoenix, for similar reasons to his use of Rust... I didn't want to have to learn it, but now I don't have to and I get to benefit from its strengths.

So far a Rust rewrite's success rate directly, probably super linearly, correlates with the presence of a good, well designed test suite. This is why Bun's rewrite and others are successful. I anticipate that this will be true for the 37Signals rewrites.

I want to learn a couple of things once they are done:

1. Once the test suite assistance is over, how do features get built in their backends and continue to maintain the same quality. LLM test writing is a bit trickier as it often favors what Randy Coulman called tautological tests back in the day. It takes a lot of work to get them not to do this, so I am guessing folks at 37Signals will read at least this part. I can't imagine zero Rust read at all.

2. Over the years they had a few innovations in their domain design, ones that Rails made easier to do, for instance their delegated type pattern. Will Rust replicate this, and how would one know without reading it, or perhaps it does not matter? Furthermore, how do newer patterns emerge? and how does our arsenal of better abstractions keep growing?

I don't have the answers but I am glad there is a chance we can learn said answers.

So the keynote mentions that in a perspective you are going to be a "maker of things" rather than a coder. But, nobody is asking, in a perspective, why would anybody use the stuff you "make" rather than using AI directly? All of the notion of apps disappears, in a perspective.

I really enjoyed DHH's keynote speech using his own family lineage story via the art history intertwined with technology evolution portrait paintings -> photography pictures as analogy of what's happening right now in the technology landscapes.

I was hoping there will be news on Rails 9.0. Feels like this is the end of Ruby Rails.

Hey is not even a Ruby Rails App anymore. And indirectly admitting Ruby is slow considering they manage to cut 99.9% of CPU with their rewrite in Rust.

I think the perf jump from Ruby to Rust is much greater than .NET Core to Rust. Not much will change in .NET land for the foreseeable future. I see this migration happening from Ruby and others so it is not surprising from that aspect.

Also - what he is talking about was true for well over a year. It is just that a lot of day-to-day gaps between prompt and output were closed in the meantime. In a sense, Ruby on Rails/37 Signals is a late adopter.

I don't understand what is supposed to come next. So its not Ruby on Rails anymore. What is it? Are agents going to magically convert all the RoR ecosystem to Rust or Whatever?

AI-psychotic and proud!

Serious question: Is there a framework that is better suited for agents? There must be something out there that makes agents fly through development with minimal token expense.

tldr:

dhh says 37signal's apps for Hey (their email platform moving to native)

backend for their email platform is now Rust - written by agents

says Rust produces small binaries - cutting number of servers needed from 110 to 10. hell they could serve peak traffic on a Raspberry Pi

says now that agents write all the code - use faster / native languages.

rails or ruby hardly get a mention besides that they might be well placed to capture web apps written by agents.

That's cool, but like with most things, I think the manager types will misunderstand:

- A lot of this is looking at an existing app and/or code for reference.

- The people doing/guiding this are skilled.

- Skilled people have thought out what to make.

Otherwise they hear "20 minutes" and think AI can spit out a logical or good product from no reference or planning.

Adieu, Ruby on Rails.

it's funeral of Ruby on Rails

This link says ‘This video is private’ to me, here’s a working one https://youtu.be/vDjW_dRyKXY

[dead]

[flagged]

[flagged]

I smell a fork coming on.

(I also smell the wild racism wafting off DHH. Really, don't give this man your attention. Don't break cordon.)

DHH is "off the Rails" is not false now?

He may be racist but what a great orator! (Who else does that apply to?) Can't really disagree with him about the AI stuff either. I mean maybe it's a bit premature but if it isn't true now it will be in 5-10 years.

I guess the death of Ruby is a silver lining to AI at least.

Talk is sponsored by Shopify, which also sponsored the Lex Fridman 5 hour promotion.

All DHH's AI opinions are sponcon.

But he has great flagging support and his perception management agency will suppress this one, too.