4 ms·

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. Not many frameworks have been thriving that long, and t

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. Not many frameworks have been thriving that long, and there's good reason. It packs everything, is tidy and productive, with a pleasant language to read and write. In the latest Stackoverflow survey, it's back at the "top 5 of desired stacks to use for next project" over a decade after its inception ! Give it a try.

axelthegerman 7mo ago
And most folks getting stuff done with Rails ain't be filling out surveys to boost their stack - or maybe that's just me. So everyone just stop worrying what everyone else thinks or seems to think and just use the right tools for you and get on with it
- wiseowise 7mo ago
  There are two types of devs: those that ship and those that fill out surveys (and not because their stacks are so much more efficient that they have time to fill out the surveys)
  - psychoslave 7mo ago
    There are two types of dichotomy: those which are autoreferring and sound, those which are absurd, and those which are really going too far.
fpauser 7mo ago
rails = ruby = oo/mutable && slow && resource hungry
- techpression 7mo ago
  And for a lot of folks that just doesn’t matter. Paying 50 or 100 USD for a server per month won’t be the thing that breaks you. Before you get to a scale where Rails become a problem you need to have a product that drives a pretty significant engagement, that’s where most fail.
mark_round 7mo ago
The "one-person framework" thing is a big draw. I'm amazed at how productive I was in it, and it's not just at the code level. Even though I've been doing sysadmin/devops/architect work for over 25 years now, it's just so damn nice now not to have to think about e.g. standing up a HA PostgreSQL cluster or Redis and deployment is largely a solved problem.
- yawaramin 7mo ago
  > not to have to think about e.g. standing up a HA PostgreSQL cluster or Redis I don't understand...Rails does not replace a HA PostgreSQL cluster or Redis, they are orthogonal. Why would you not have to think about them?
etothet 7mo ago
Over TWO decades! Rails has been around since 2004, making it just slightly younger than Django. edit: Django was release in 2005
- sarchertech 7mo ago
  Rails is definitely older than Django. Django wasn’t released publicly until 2005. Django had private use before then, but rails was also in private use before it was released.
  - pushcx 7mo ago
    Rails's public release was July 2004: https://rubytalk.org/t/ann-rails-0-5-0-the-end-of-vaporware/12744 https://rubytalk.org/t/ann-rails-0-5-0-the-end-of-vaporware/... Django's was July 2005: https://www.djangoproject.com/weblog/2005/jul/15/chipy/ https://www.djangoproject.com/weblog/2005/jul/15/chipy/
    - etothet 7mo ago
      Adding Simon Willison's announcement: https://simonwillison.net/2005/Jul/17/django/ https://simonwillison.net/2005/Jul/17/django/
  - etothet 7mo ago
    Thanks for the correction!
monooso 7mo ago
Two decades. Rails was released in 2004, IIRC.
miguno 7mo ago
> In the latest Stackoverflow survey, it's back at the "top 5 of desired stacks to use for next project" over a decade after its inception ! Oh, where did you find that? Only info I could find was that Rails is at rank 10 in the Web Frameworks category for Admired vs. Desired in the 2025 survey: https://survey.stackoverflow.co/2025/technology/#2-web-frameworks-and-technologies https://survey.stackoverflow.co/2025/technology/#2-web-frame....

axelthegerman 7mo ago

And most folks getting stuff done with Rails ain't be filling out surveys to boost their stack - or maybe that's just me. So everyone just stop worrying what everyone else thinks or seems to think and just use the right tools for you and get on with it

wiseowise 7mo ago
There are two types of devs: those that ship and those that fill out surveys (and not because their stacks are so much more efficient that they have time to fill out the surveys)
- psychoslave 7mo ago
  There are two types of dichotomy: those which are autoreferring and sound, those which are absurd, and those which are really going too far.

fpauser 7mo ago

rails = ruby = oo/mutable && slow && resource hungry

techpression 7mo ago
And for a lot of folks that just doesn’t matter. Paying 50 or 100 USD for a server per month won’t be the thing that breaks you. Before you get to a scale where Rails become a problem you need to have a product that drives a pretty significant engagement, that’s where most fail.

mark_round 7mo ago

The "one-person framework" thing is a big draw. I'm amazed at how productive I was in it, and it's not just at the code level. Even though I've been doing sysadmin/devops/architect work for over 25 years now, it's just so damn nice now not to have to think about e.g. standing up a HA PostgreSQL cluster or Redis and deployment is largely a solved problem.

yawaramin 7mo ago
> not to have to think about e.g. standing up a HA PostgreSQL cluster or Redis I don't understand...Rails does not replace a HA PostgreSQL cluster or Redis, they are orthogonal. Why would you not have to think about them?

etothet 7mo ago

Over TWO decades! Rails has been around since 2004, making it just slightly younger than Django. edit: Django was release in 2005

sarchertech 7mo ago
Rails is definitely older than Django. Django wasn’t released publicly until 2005. Django had private use before then, but rails was also in private use before it was released.
- pushcx 7mo ago
  Rails's public release was July 2004: https://rubytalk.org/t/ann-rails-0-5-0-the-end-of-vaporware/12744 https://rubytalk.org/t/ann-rails-0-5-0-the-end-of-vaporware/... Django's was July 2005: https://www.djangoproject.com/weblog/2005/jul/15/chipy/ https://www.djangoproject.com/weblog/2005/jul/15/chipy/
  - etothet 7mo ago
    Adding Simon Willison's announcement: https://simonwillison.net/2005/Jul/17/django/ https://simonwillison.net/2005/Jul/17/django/
- etothet 7mo ago
  Thanks for the correction!

monooso 7mo ago

Two decades. Rails was released in 2004, IIRC.

miguno 7mo ago

> In the latest Stackoverflow survey, it's back at the "top 5 of desired stacks to use for next project" over a decade after its inception ! Oh, where did you find that? Only info I could find was that Rails is at rank 10 in the Web Frameworks category for Admired vs. Desired in the 2025 survey: https://survey.stackoverflow.co/2025/technology/#2-web-frameworks-and-technologies https://survey.stackoverflow.co/2025/technology/#2-web-frame....