Ask HN: Is my preference for RubyOnRails over Laravel justified? | Hacker News Reader

Ask HN: Is my preference for RubyOnRails over Laravel justified?

4 pointsgitrog4 comments

A colleague and I are going through the planning phase of building a web app for specialist users. We should have about 20k concurrent users daily. His previous experience has only been with Laravel, and although I've used several frameworks, my main experience has been using Django and Rails, and in recent years I've begun favouring Rails heavily for the development experience.

We're now trying to come to an agreement on which framework to use. My main two arguments for going with Rails was that: 1 - Rails has amazing support for its features (additionally, I'm not convinced that Laravel has feature parity with Rails as he suggested) 2 - I've never met a PHP developer who tried Python or Ruby and ever wanted to go back, including myself. (I chalk this up to the development experience)

These are not the strongest arguments, but I believe most people think that the choice comes down to preference anyway. At least, I've never really read an article that made any stronger case than that.

So is there a more objective position to take here? Are there any real reasons to use one framework over the other?

> Are there any real reasons to use one framework over the other?

1. Programming language ecosystem/Framework ecosystem/Developer support/Tutorials/Books

2. Framework maturity - has it been around for a while to have gone through a development

3. Ease of finding developers in the future

4. Ongoing support and development - has the required support to address security concerns, bugs and issues.

5. Most importantly - which one are you most comfortable with.

Just my humble opinion :-)

Hope it helps!

Would you say either framework has much over the other on each of these points (besides point 5 - of course)?

That's kind of more what I'm wondering about.

I moved from Rails to Laravel about 7 years ago, I think Laravel has the better ecosystem and community now. Rails is great so you probably couldn't go wrong choosing either.

I think Laravel has better coverage with packages/gems and community involvement.

Checkout Laravel Livewire (I expect it's similar to New Magic that @DHH is working on open sourcing for Rails). Livewire has been amazing to work with.

Laravel Jetstream, Auth 2FA, profiles out of the box

These are paid but well worth it:

Laravel Forge, create and deploy Envoyer Zero, Downtime deployment Laravel Vapor, serverless on AWS

Good luck with your web app.

If you have also used laravel then that's probably the best option. No need to get your colleague to learn another framework. Also larvel is pretty great nowadays :)

Reply on news.ycombinator.com