- 25comments
- 13comments
- 349comments
- 11comments
- —discuss
- 1comments
- 94comments
- 116comments
- 206comments
- 8comments
- 50comments
- 31comments
- 36comments
- 365comments
- 591comments
- 150comments
- 26comments
- 369comments
- 133comments
- 403comments
- 10comments
- 18comments
- 54comments
- 43comments
- 22comments
- 127comments
- 22comments
- 648comments
- 22comments
- 18comments
From the talk it’s clear, Rails needs to be forked.
isn't https://mosscap.dev/ a fork?
I think one can just wait till DHH loses interest, can't be long now.
While I mostly agree with DHH's take on this particular technological cycle, this is a very well thought out criticism.
Rails, or even more so php have VERY little to bring to the table in 2026 going forward. Rails (ruby) is still a saner language than PHP, but as slow as php is. (granted ruby is not idiotic like PHP and runs rather than start/die).
If you go the LLM route something like Go is probably the goto default for MOST networking/web-first apps. You get static types, and a fast compile cycle (rust is still very slow here), and IF you want more from the language you can use something like Lisette (https://lisette.run/).
Bottom line is dynamic languages are obsolete. There is really no benefits from using them outside very small throw away scripts.
Well that's not something you say in a Rails conference, best language or framework for a project has been debated before I was born and will continue to be
The summary is exactly why a lot of people is upset.
I've seen this one a few times lately. People should stop building UIs, nobody wants to interact with a UI. Everyone's app should just be an API that you can use with a chatbot. Except for my app — my app is a handcrafted miracle of artisanal UX and its UI will change the way you see the world.
It's exactly the old argument, just now with LLMs in the place of shell pipelines: in terms of functionality and value to users, software ought to be malleable and composable. We've known it since the eighties. But the model of selling a piece of software as a product as if it were a pair of shoes is incompatible with that. You need a big monolithic application to justify users paying a bunch of money for it, and you need it to have a fancy interface that makes an impression. And the whole software industry is built on top of that model. Where monolithic software is completely unfit for a purpose, like when it needs to be a component of a larger system, we rely on (mostly unpaid) OSS.
Except now LLMs let you, with very little technical know-how, plaster a ‘programmable’ interface on top of unstructured data/interface meant for humans, and because that's what we actually want, of course everybody does that. So the end result is a wildly expensive pipeline from API to UI and back to API again. I wonder how long the legacy ‘human-oriented’ layer in the middle, and the industry that's been built on top of it, will last.
(Separately, chatbots are not great as a UI for most things, and the problem of building the universal UI still also stands. But it turns out for a lot of things people would rather have a bad universal UI than a good special-purpose UI for each task.)
Rails is dead.
It’s founder has converted to AI driven Rust.
DHH will bring his tribe of true believers to where he has gone, where he has set up a new sideshow tent.
Do you follow the leader.