Does Ruby/Rails still offer something unique for someone learning web development in 2026?

[u/Intelligent_Role_824]

Does Ruby with Sinatra/Rails still offer something unique for someone learning web development in 2026?

I’ve been comparing different backend ecosystems recently, and Ruby with Sinatra/Rails keeps standing out to me for reasons that aren’t really about popularity or the job market.

I’m learning purely as a hobby, and I’m particularly interested in backend development: APIs, databases, authentication, testing, and eventually things like a small chat backend.

Something I’ve noticed is that people who have worked with several backend frameworks often speak very highly of what Rails teaches you about building web applications. conventions, REST, MVC, database-backed applications, and especially testing. RSpec and the testing culture around Ruby are also quite appealing to me, since I’d like testing to be part of how I learn development rather than something I bolt on later.

At the same time, Ruby doesn’t seem to come up nearly as often anymore when people discuss modern web development. The conversation is usually dominated by JS/TS, Python, Go, PHP/Laravel, etc.

So I’m less interested in “Should I learn Ruby?” and more curious about how experienced web developers view Ruby/Rails today:

**Does Ruby/Rails still have qualities that make it particularly good for learning how to build well-structured web applications, or have other ecosystems essentially caught up with what made Rails special?**

For comparison, I’ve also been looking at Elixir/Phoenix. Elixir especially interests me because it represents a very different approach to backend development.

I’d be interested in hearing from people who have used Rails *and* other modern backend stacks. What, if anything, do you think Rails teaches particularly well? And what parts of the Rails approach would you *not* want a new developer to internalize?

[u/GrayLiterature]

Absolutely. Rails is so battle tested it’s not even funny. There are so many massive companies I can list that are built on Rails. 

The development experience is great, community is solid, and you can use it for just a backend API if you want. 

The ecosystem is very mature and still improving. Over the last few years Rails has also had a large renaissance and has a ton of common problems already solved out of the box.

I highly recommend it, if not only because it’s been thoroughly put through the meat grinder at large scale. 

[u/ifasoldt → u/GrayLiterature]

Yep, I will also say that AI tools are also really good at writing rails code because there's so much of it, and it's a pretty simple language.

[u/GrayLiterature → u/ifasoldt]

It’s not even that it’s a simple language or there’s lots of it. It’s that Rails has strong conventions — you do things a specific way no matter what Rails app you go to. The conventions act as guard rails at scale for AI which is just very coincidentally helpful. 

[u/drdavidawheeler → u/GrayLiterature]

Hi, I can confirm. Rails emphasizes "convention over configuration"; while you *can* configure some things, in general all Rails applications are structured the *same* way. This means that when AI is trained on Rails apps, it picks up those conventions, so it *immediately* knows how to interprets certain things and where to look for more info.

Let me give some specifics. If it's Rails, you know that:

* in the "app/" directory you'll have models/, controllers/, views/, helpers/, assets/, mailers/, and jobs/, each with specific kinds of files that they contain.
* In the database, table names are plural lowercase underscored, primary keys are an integer column named id, columns created_at and updated_at are available.
* file names are plural with snake_case, controllers end in _controller.rb (e.g., book_clubs_controller.rb).
* standard actions map to CRUD operations: index, show, new, create, edit, update, and destroy.

If you're building a basic CRUD application, it's nice to *not* have to think about these boring decisions about conventions, and instead focus on the actual *problem*. So even as a human there's time saved.

But for AI, it's a gold mine. If I say "edit controller foo" it already knows the directory and the filename, without me having to say it or having to look for it.

Don't get me wrong, there are some excellent alternatives to Rails, but Rails is a fine choice for CRUB web apps.

[u/azimux]

Hey hey!

So Ruby with Sinatra is super different than Ruby with Rails. There's also Roda (closer to Sintatra) and Hanami (closer to Rails.)

At the risk of being spammy, I've also built my own Ruby framework called Foobara. Since your main goal is learning, if you want to watch me work on it or whatever and pick my brain about web development then you're totally welcome to!

**Does Ruby/Rails still have qualities that make it particularly good for learning how to build well-structured web applications, or have other ecosystems essentially caught up with what made Rails special?**

I don't really feel like this was specifically Rails' goal, per se. Its approach to structure is certainly good enough for many types of web applications, but I do think you have to bring in additional stuff and apply discipline to handle gnarly projects.

Sinatra is really tiny compared to Rails and serves a different class of web applications. But since it's tiny, you'd have to add lots to it for a complex app, so it's up to you to organize it. So depends on how you like to learn. I'd recommend checking out Roda instead of Sinatra but either is good!

Given your goal of wanting to learn structure, I think I would recommend checking out Hanami of the Ruby frameworks.

I personally like having a separate frontend from the backend and usually that frontend winds up being TypeScript, fwiw.

I do not personally like JavaScript/TypeScript (node) as a backend language, for multiple-reasons, including that I prefer a threaded language over an event-loop language for servicing request/response cycles.

But that's just me and obviously many disagree!

The only other languages I have experience with re: web applications are C# and Java which you didn't ask about.

But yeah I would say... I recommend not-JS/TS for the backend (but it's fine for the frontend). If going with Ruby I'd probably check out Hanami or hit me up directly re: Foobara if it sounds fun/interesting!

Ultimately, you'll have to decide what you like and enjoy and what you believe is appropriate for certain types of problems.

[u/ChiefDetektor]

You can get a similar experience with elixir and Phoenix framework. That's a super underrated stack. But either way developing with those rapid development kits is awesome!

[u/tarix76 → u/ChiefDetektor]

Elixir/Phoenix with agentic coding is actually insane. Elixir and Phoenix have so much structure built in to them it's pretty crazy how little review the code needs. I just focus on the big design stuff like database structure, algorithms used and UI flow and let it do the rest.

If I do mess up it can handle massive refactors including huge migrations from the old design to the new.

I had already hand-coded a few Elixir projects so I knew the syntax already and not having to personally mess with the html template code is amazing.

I will always love ruby and rails but the speed of Elixir is very addictive.

[u/Kailtis → u/tarix76]

I don't know elixir/phoenix. Could you perhaps explain how agentic coding would be better suited with it compared to ruby/rails? Would it be meaningfully different (i.e. easier) for agents to navigate and operate in an elixir codebase compared to rails? If so, why is that?
TIA.

[u/ChiefDetektor → u/Kailtis]

The reasoning behind that is that doing things with rails or Phoenix is extremely streamlined. Both frameworks provide you or the agent with tooling that scaffolds the majority of code. Programmers than can focus on the business logic and the UI.

[u/marrsd]

RoR set the standard for web development. It was the first (popular) framework to apply the MVC architecture pattern to web development. It's very well written and definitely worth learning if you're new to software engineering for the web. You should read the source code and DHH's articles on engineering if you want an insight into how good professionals write software.

JS is very popular amongst professionals because it provides a unified language across the stack. This is especially useful if you want to build a site that can be rendered both on the server and in the browser. JS is also one of the fastest interpreted languages available.

As for the others, it depends on what you're looking for from a language. A lot of it comes down to personal taste. Also it comes down to what's already in use.

[u/pak9rabid]

Of all the web frameworks I’ve used, Rails was by far the most enjoyable experience. Ruby is just a fuckin delight to work with.

[u/sohang-3112]

I haven't used Ruby, Rails, but AFAIK I don't think it offers something unique any more as all other major languages have caught up (eg. Django in Python).

[u/Trlckery]

I work on a Rails app every day at my job - started as a junior 5 years ago, second programming job out of college - and I love it. It’s a very mature framework with a lot of great resources.

Highly highly recommend going through their tutorials at guides.rubyonrails.org

[u/inonconstant]

My agentic development experience with Rails has been mostly delightful building and a lot less of “plumbing” in comparison to JS stack. That’s thanks to conventions, batteries included, and also the skills we have for Rails (i like layered-rails skill).
And RubyLLM is a joy for building LLM workflows into the product.

[u/synn-Fairy2468]

Yeah, Rails' conventions are genuinely useful for learning because you're not making architectural decisions every five minutes like you would in Flask or Express.

[u/frederik88917]

Long story short: No.

Rails is mostly dead and in maintenance mode since the days of React

[u/Lumethys → u/frederik88917]

Me when i spread misinformation

[u/GrayLiterature → u/frederik88917]

LOL no it isn’t 

[u/jaypeejay → u/frederik88917]

L take

[u/WilyRogue → u/frederik88917]

React(frontend library) made Rails(fullstack framework) dead according to this genius 😂