Ruby on Rails

Rails influenced some other popular web frameworks, and I feel it’s still faster to build some types of web apps in Rails. I’d think you could cover more concepts sooner and then translate what you’ve learned to other frameworks as you need them.

I am one of those obnoxious people who is trying all the time new web technologies, without deepening the skill for years in just one. Out all the frameworks I have used (Django,Phoenix,Node/Express in all its flavors,.NET Core, Echo) Rails is by far the one in which I feel more productive. Ruby is a lovely language, the ecosystem is mature, there is always a gem for everything and for the kind of applications I do (just 1-3 developers) Rails suits the needs perfectly. All the rest have bee

Ruby on Rails is still the best at what you're describing if it's a web app.

Ruby is a very beautiful language both in logic and consistency. Rails is a mature framework. The ecosystem is very much alive albeit not “exciting” anymore and at the end of the day people use what they know. The 2010s have produced a large number of Rails developers. For the majority of CRUD apps Rails (or Laravel or Django) are just fine thus there’s no need to really make a switch. Finally, React can power a lot of things but in my experience it is far from offering the right integration and

In my opinion: Ruby On Rails. It has an awesome community, lots of gems (libraries) for web stuff. An opinionated way of doing frontend and backend. No waste of time taking decisions about what state management to use, how to organize stuff, etc. Just focus on stable, accepted, well maintained conventions and focus on your business problems instead.It might be harder to find people interested in working with it depending where you are, but I guarantee you that you will need a lot less people

I have not looked into Elixir Phoenix but have been hearing some noise about it recently. Folks also frequently compare Rails to Django (Python) ... my 2 cents is Rails has a lot of good tools to build web apps fast and underneath it all provides a lot of strong functionality. Most things are relative though to the specific "thing" you're building so I can not say Rails is the best framework without knowing xyz, but for most web applications I'd stick with Rails. You get a lo

I would suggest that the Rails scene is at least worth checking out.I’ve seen a number of people move from .NET or Node to Ruby and Rails and thoroughly enjoy it, with little desire to go back. For reference, the last 12 years I’ve worked for a company that was traditionally .NET. In the past few years, we’ve been choosing Rails instead. Once you know its conventions, you can really fly. It’s very mature and doesn’t often change in frustrating ways. What I learned in 2014 is still very releva

Surely you don't think that Rails is better than everything else in every single respect? There are plenty of frameworks that are simpler (Flask/Sinatra), faster (Play, etc.), support lightweight concurrency better (node.js based, Play too, etc.), have much better IDE support (ASP.NET MVC), support client/server partitioning (Meteor/Opa), and so forth.

Comparing Rails to Express is not apples to apples. You should compare Rails to something like Next.js that has a lot of the magic and plumbing taken care of for you on both the front end and the back end.I agree that for side projects, underfunded startups and especially for product/business-focused founders, using the quickest magical prototyping framework is definitely the best idea so I agree with the overall sentiment of the post, just not the specific conclusion that Rails is the b

RUBY/RAILS. As productive as Django. More books, good community and so on.