Ruby on Rails
Full-stack, server-side web application framework for Ruby built around convention over configuration.
HN commenters like Rails for batteries-included productivity on CRUD and SaaS web apps1234, especially for solo developers and early-stage products567, and for its mature conventions and large ecosystem.8910 The most common caveats are friction once an app strays from standard CRUD patterns111213 and the lack of static typing in large codebases.1415
Why people recommend it
Productivity · 3
Commenters say batteries-included Rails lets them build and ship quickly.
“Ruby and Rails both go out of their way to provide the developer with as much power as they can.”
“For solo devs, Rails is arguably most productive webapp system.”
Show 1 more
“Since them I'm on Rails.”
CRUD web apps · 3
Seen as a top choice for CRUD and server-rendered web apps over SPAs.
“Rails for straight up CRUD is top, autogenerated things etc”
“something as batteries-included and expressive like Rails or Django”
Show 1 more
“90% of the SPAs I use could be Django/Rails/Flask apps with no noticeable difference”
Mature ecosystem · 3
Praised as battle-tested, with a massive ecosystem and shared conventions that age well.
“the reason we use Rails is pretty simple…it’s great, it’s battle tested and has a massive ecosystem.”
“This is why I use Ruby on Rails. Shared constraints and boring conventions age better than clever mini-frameworks”
Show 1 more
“I've been a Rails DevOps and nowadays a web one-man-show with it for over 10 years and I'd do it again.”
Pleasant code · 3
Users enjoy writing Ruby with Rails and value its focus on beautiful, simple code.
“It’s been a real pleasure getting back into Ruby after so many years in typescript, python, and rust.”
“I have been using Rails for over a decade now and always liked the focus on writing beautiful and simple code.”
Show 1 more
“the beautiful code family we used to have with Rails and Django”
Works with LLMs · 3
Some find AI agents write Rails code well and can use the built-in console.
“For solo devs, Rails is arguably most productive webapp system.”
“Rails dev here, still using it, still plan on using it, use agents”
Show 1 more
“Simply Ruby on Rails.”
Caveats and dissent
Non-standard requirements · 3
Apps that don't fit the standard CRUD pattern or need unusual features can be hard to build, and the implicit 'magic' can get in the way.
“Rails for straight up CRUD is top, autogenerated things etc”
“Since them I'm on Rails.”
Show 1 more
“implicit object function magicks (rails)”
No static typing · 2
Large untyped Rails codebases are described as painful, though Sorbet is suggested as a mitigation.
“I love Rails, but after working for a few places with huge Rails codebases and then several other places with .NET and other frameworks with actual typing, I just can't go back to Rails”
“I would happily work on a Rails system today too.”
Community controversy · 3
Some commenters cite controversy around Rails and DHH as driving developers away.
“now that Rails has a lot of controversy and not really worth then of course users dropped off.”
“although I used Rails for a few personal projects”
Show 1 more
“I have been using Rails for over a decade now and always liked the focus on writing beautiful and simple code.”
Learning curve · 3
Newcomers may struggle with the app structure and with docs that assume prior Ruby/Rails knowledge.
“I love rails and the recent improvements are great.”
“the documentation kind of assumed you already knew a lot about Ruby and indeed Rails”
Show 1 more
“Once you know it, you'll be very fast. I loved it when I used it professionally.”
Resource usage · 1
One user cut peak memory from 700MB to 60MB by moving apps to a Rust framework.
“Rails was truly wonderful in its heyday”
Upgrade maintenance · 1
Updating years-old projects and their dependencies takes significant time.
“I love the batteries that RoR or Django gives you, but then I also remember how much time it takes to maintain old projects.”
Often compared with
Who recommends it in their own words
Threads where it came up
- Returning to Rails in 2026 7 mentions
- What About Rails? 3 mentions
- Rails World 2026 Opening Keynote [video] 3 mentions
- Show HN: Rails UI 3 mentions
- Does Ruby on Rails still make sense? 2 mentions
- Hanami 3.0: In Full Bloom 2 mentions
Also written as Rails. Data: ruby-on-rails.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 42
“Things I think make sense for Rails in the LLM era:”
“Rails was truly wonderful in its heyday”
“So I now no longer use Rails for new projects.”
“I spent years as a Rails dev”
“small Ruby on Rails sites on a single $10 vps”
“Twenty years ago, for a brand new web framework written from scratch, and by then they had already fixed it.”
“something as batteries-included and expressive like Rails or Django”
“I really appreciate Rails and DHH's approach though”
“Ruby and Rails both go out of their way to provide the developer with as much power as they can.”
“Once you know it, you'll be very fast. I loved it when I used it professionally.”
“Rails dev here, still using it, still plan on using it, use agents”
“I work in Rails too, I try to keep them to a minimum”
“now that Rails has a lot of controversy and not really worth then of course users dropped off.”
“into a rails app (that hosts both draw.city”
“rails, because it's what I regularly use”
“Since them I'm on Rails.”
“The depth sits in Rails and Postgres”
“I've recently added RSS and other alternative representations to our Rails based ecom store[1] and rails makes it super easy[1a].”
“The product is a fairly standard Ruby on Rails webapp”
“Django, Laravel, and Rails are very neat.”
“the reason we use Rails is pretty simple…it’s great, it’s battle tested and has a massive ecosystem.”
“although I used Rails for a few personal projects”
“implicit object function magicks (rails)”
“I have been using Rails 8 for the past few months on a work project”
“For web apps, Rails, Django, Laravel.”
“Mine is pretty vanilla ruby on rails”
“90% of the SPAs I use could be Django/Rails/Flask apps with no noticeable difference”
“Github was a lot simpler when it was still just a Rails app.”
“since we use Rails we can have it query the tables apart and join the tables through the defined model”
“Simply Ruby on Rails.”
“RoR is.. "good enough".”
“For solo devs, Rails is arguably most productive webapp system.”
“I’m a Rails guy myself”
“Switched from Spring Boot to Ruby on Rails 3 years ago.”
“I would happily work on a Rails system today too.”
“I love Rails, but after working for a few places with huge Rails codebases and then several other places with .NET and other frameworks with actual typing, I just can't go back to Rails”
“Rails for straight up CRUD is top, autogenerated things etc”
“I love the batteries that RoR or Django gives you, but then I also remember how much time it takes to maintain old projects.”
“I've been a Rails DevOps and nowadays a web one-man-show with it for over 10 years and I'd do it again.”
“I love rails and the recent improvements are great.”
“only Ruby on Rails world seems to systematically care about devx and infra friction”
“This is why I use Ruby on Rails. Shared constraints and boring conventions age better than clever mini-frameworks”