You choose Rails because you can build extremely fast with it (for a variety of reasons). The number one risk to a startup is not finding product market fit. Therefore, building fast is paramount. It doesn't matter how much load your product can handle if you never get the load in the first place.
I would absolutely recommend Rails for most startups whose central product is a web application.
> I would absolutely recommend Rails for most startups whose central product is a web application.
I think that depends on the product. I'm working on your usual "unbundling Excel" product, and I don't see what Rails has to offer over Django or Laravel. Maybe Rails has a better integration for "you don't need to write JS" stuff like Hotwire? But other than that, I don't think Rails is still the silver bullet that it once was.
Django and Laravel are both fine options, yes. Depends on the talent and network you already have really. The point is use an MVC framework with a mature ecosystem.
I tend to disagree, this was true few years ago but there are now tons of frameworks / boiler-plates which also enable devs to launch fast and stay fast e.g Phoenix
Yes, Rails is very mature but the difference is not that huge anymore.
Yes. Because Rails decided what the "Golden path" was 10 years ago, but pales when having to do real-time anything, concurrent anything, parallel anything, etc. also, scaling tends to be expensive.
I will admit that rails ecosystem is much larger and often you have multiple libraries that do the same thing and you can pick and choose and those gems/libraries have been around for a while.
Phoenix you can spin up a SaaS platform with realtime messaging and event handling the way you could spin up a blog with rails 10 years ago.
I would absolutely recommend Rails for most startups whose central product is a web application.