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.
also worth noting that hotwire is dead according to DHH in this talk. The rendering html server side is old way now
Where did he say that? I listened to it yesterday and AFAIK he only said "I don't know where the line between native vs web will end up in the future" (now that we can generate native apps easier)
Keep in mind DHH is working on an email app, it makes sense he sees native as the default option for that over pushing everything through the web when the barrier to entry lowered dramatically.
Hotwire is not explicitly a cross-platform concept. It's primarily a way to build web apps in the browser which is not going away any time soon. The only difference is in 2026 you're just more likely to vibecode a native mobile app than build a web/React Native version. Likewise you may build a native Desktop version instead of an Electron wrapper.
The issue with native apps is that you have to convince people to install them. If I had one app for each tab I open in my browser my phone would be a mess and out of free space. Then you slow down the delivery of features and bug fixes because you have to go through the app stores. You can't deploy something every day or more often.
So even if we can generate an app easily now, is that a wise choice for every business?
Like everything, depends on the usecase. An email desktop app seems to be a valid one. A standard earlystage B2B SaaS Rails web app? Not so much.
Same with server side rust. A high volume transactional backend email service makes sense there. The base layer of a CRM managing a lot of business logic?
Life will go on much the same. We just have more options to say yes to 'native' with LLMs, we can experiment more with ideal scenarios rather than a religious adherence to cross platform or single-framework merely for team DX simplicity.
When I started in computing there was no Web, there was enough space to install the applications that actually mattered, and even better, developers actually had to take hardware constraints into account.
If the apps were actually good, you'd install them. A lot of the apps on F-Droid are pretty lightweight, and a phone's security model makes it much safer than installing apps on Windows.
The web makes apps worse by forcing a fairly strict sandbox, even as Google keeps trying to loosen it. Think of a messaging app that hides in your notification tray, that's a trivial UX thing that's impossible on the web.
Rendering HTML on the server was kind of how IBM mainframes talked to their 3270 terminals, only that HTML is a lot nicer than 3270 streams and HTTP is human readable.
Server side rendering makes sense for mostly static content, but for web applications, a front end framework and a back-end API are a much better match.
Uhh, sounds like you haven't been writing modern React lately, which is server side lol
and something about omarchy