2 ms·
I don't think either is objectivly better - if for no other reason than ruby and php being quite different languages. Personally I much prefer ruby - but I cou
by e12e 5y ago
I don't think either is objectivly better - if for no other reason than ruby and php being quite different languages.
Personally I much prefer ruby - but I could perhaps see myself reaching for Laravel for a project depending on requirements.
- jmcharnes 5y agoAs a Ruby developer I resonate with this. I love a LOT about the Laravel ecosystem, but I also still really love Ruby and Rails.
- jstummbillig 5y agoWhat requirements does Laravel meet that Rails does not?
- yurishimo 5y agoMarginally cheaper/easier to deploy. Very robust queue system built in. Where you'd pay for Sidekiq in Rails, that's included in Laravel. Auth is also more streamlined since Laravel takes a stance on what the default is unlike Rails (though I admit most people just use Devise). I think PHP is still faster as a language? There are also tools available now to run Laravel apps on serverless infrastructure if that's something you don't want to mess with. I'll admit I'm biased and haven't spent much time with Rails outside of a hello world and various podcasts.
- e12e 5y agoI'm guessing it's feasible to deploy to shared hosting for example?