If I had a nickel for every time a "State of Web Dev" article declared Ruby on Rails dead, I wouldn't need to write code for a living.
Since roughly 2012, Rails has been the favorite punching bag of the tech industry. It’s "too slow," it "doesn't scale," and it’s "not modern." Yet, in 2026, some of the most successful companies in the world (Shopify, GitHub, Airbnb, Coinbase) still run on it. Even more interesting? A new generation of indie hackers is ditching the "Modern Web Stack" and coming back to the Monolith.
Why is Ruby on Rails still alive? Because it stopped chasing the hype and started focusing on The One-Person Framework.
1. The Javascript Fatigue is Real
For years, the industry pushed the idea that you must have a decoupled architecture: a JSON API on the back and a heavy SPA (React/Vue) on the front.
But developers eventually hit the Complexity Wall. They realized they were spending 50% of their time just managing the "state" between the two layers.
Rails stepped in with Hotwire. By sending HTML over the wire instead of JSON, Rails allowed developers to build fast, reactive, "modern" feeling apps without the overhead of a complex JS build pipeline. People are staying with Rails because they realize they can build 90% of a React app with 10% of the code.
2. Rails 8: The Zero-Tax Stack
Rails 8 has doubled down on the "One-Person Framework" philosophy. The mission is simple: A single developer should be able to deploy a world-class application without a DevOps team.
- Solid Queue & Solid Cache: Removed the "Redis Tax." You can run your whole app on a single database.
- Kamal: Removed the "PaaS Tax." You can deploy to a cheap $5 VPS as easily as to Heroku.
- Thruster: Removed the "Nginx Tax." Your app is production-ready out of the box.
Rails is alive because it is actively making itself cheaper and easier to run than the competition.
3. Ruby: The Language of Happiness
We often forget that Ruby was designed by Yukihiro "Matz" Matsumoto specifically to make developers happy.
Ruby’s syntax is as close to English as a programming language gets. It is expressive, elegant, and stays out of your way. In a world of strict types and verbose boilerplate, writing Ruby feels like a breath of fresh air.
Developers stay with Rails because they actually enjoy the act of writing the code. Happiness leads to productivity, and productivity leads to shipped products.
4. The "Boring" Advantage
Stable software is "boring," and boring is good for business.
When you write a Rails app today, you aren't worried that the underlying routing library will be deprecated in six months. You aren't worried that the "standard" way to fetch data will change three times this year.
The Rails ecosystem is mature. The gems (libraries) are battle-tested. The documentation is exhaustive. This stability allows you to focus on Business Logic rather than Infrastructure Maintenance.
5. It Scales (Stop Lying)
The "Rails doesn't scale" argument died years ago.
- Shopify handles over 1 million requests per second on Rails.
- GitHub manages the world’s code on Rails.
Does it require more hardware than a raw C++ or Go server? Yes. But developer time is more expensive than server time. Rails allows you to scale your team and your feature set faster than almost any other framework, and you can always throw a few more $40 servers at a performance bottleneck.
Summary
Rails isn't just "alive" - it’s in a Renaissance.
It has become the premier choice for the solo founder, the indie hacker, and the small team that wants to outpace the giants. It has stopped trying to be "cool" and started being "effective."
If your goal is to talk about technology on Twitter, learn the newest JS framework. If your goal is to build a business, learn Rails.
Are you a Rails veteran or a new convert? Let's discuss why you’re still here (or why you came back) in the comments! 👇
Top comments (0)