You’ve felt it. That creeping sensation that the tools you’ve relied on for a decade are suddenly on the wrong side of history. For years, Ruby on Rails was the undisputed king of web development. It made us fast. It made us productive. It let a single developer build an empire.
But the world has shifted beneath our feet.
When human time becomes free, machine time becomes the ultimate luxury.
Think about it. Rails’ entire value proposition was a trade-off: it sacrificed machine performance to save human developer time. It ate RAM and CPU cycles for breakfast so we wouldn’t have to write boilerplate code. In 2010, that was a brilliant bargain. Developers were expensive; servers were relatively manageable. Fast forward to today, and an LLM can write a Rails app in seconds. The cost of human coding has plummeted to near-zero. But have you checked your AWS bill lately? Cloud infrastructure and hardware costs are now the dominant constraint.
We optimized for the most expensive resource in the room. Then we made that resource free.
The same productivity gains that made Rails revolutionary have now become a liability. If AI can write code instantly, why are we paying a premium to host bloated, runtime-inefficient applications? The bottleneck is no longer the developer typing in the IDE—it’s the server executing the code.
This is where the paradigm flips. We need to stop obsessing over developer speed and start obsessing over runtime efficiency. Ecosystems like Elixir and Erlang, built on 25 years of telecom battle-testing, suddenly make perfect sense. Elixir gives you the human productivity without the performance costs. It handles concurrency beautifully, sips resources, and scales without demanding a firstborn child from your cloud provider.
The market’s incentives have fundamentally flipped. If you are still choosing frameworks based on how fast a human can write them, you are fighting the last war. The new war is about total cost of ownership, and that means runtime efficiency is king.
The framework that won the developer productivity war is about to lose the runtime efficiency war.
Rails had a legendary run. It taught us to love developer happiness. But in a post-LLM world where code writes itself, the only thing that matters is how cheaply and efficiently that code can run. It’s time to let go of the past and start building for the actual constraints of today.
FAQ
Q: Isn't developer experience still important if LLMs are just writing the code?
A: Developer experience matters, but it's no longer the primary cost driver. When AI writes the boilerplate, the human's job shifts to architecture and optimization. You need a framework that supports that, not one that hides inefficiency behind developer convenience.
Q: What's the practical implication for my next project?
A: Stop optimizing for how fast you can ship an MVP. Start calculating the Total Cost of Ownership (TCO) over the lifecycle of the app. If runtime and cloud costs are your biggest expenses, choose a performance-optimized ecosystem like Elixir over Rails.
Q: Is Rails actually dead, or is this just hype?
A: Rails won't disappear overnight, but its competitive advantage is gone. For new, large-scale projects where cloud costs matter, Rails is a liability. It's the difference between being a legacy system and being a forward-looking architecture.