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.

▲

mark_round 4 hours ago | parent | next [-]

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.

▲

axelthegerman 4 hours ago | parent | prev | next [-]

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 4 hours ago \| parent [-]
		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)

▲

etothet an hour ago | parent | prev | next [-]

Over TWO decades! Rails has been around since 2004, making it just slightly younger than Django.

▲

sarchertech 41 minutes ago | parent [-]

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 2 minutes ago \| parent [-]
		Rails's public release was July 2004: 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/

▲

fpauser 4 hours ago | parent | prev [-]

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

	▲	techpression 27 minutes ago \| parent [-]
		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.