imho, as someone who was almost a Ruby on Rails dev, because of gems, and the ease of adding packages. When laravel hit, and composer got popular that was a moo

imho, as someone who was almost a Ruby on Rails dev, because of gems, and the ease of adding packages. When laravel hit, and composer got popular that was a moot point, and php being more widely used on shared servers which was more popular w/ small clients for being 'cheap', I went w/ laravel and honestly laravel feels way more polished... For example even now with Rails you need to role your own authentication system (95% of the time that's devise) and a lot of other things baked into Laravel you need to figure out on your own, and I think they've switched asset provisioning/build systems a bunch of times, laravel has a few but each one sunset the previous mostly, except mix and vite are kinda still both in production, vite I think will probably become the defacto before long in most new projects. PHP is beautiful since 7.0, and keeps getting better. Before 7 and Before composer it was just a hackety POS, and didn't look appetizing at all, there's definitely sexier languages/frameworks out there that have 10x the reqs/second than php can get, but there's costs w/ that - and that's usually length, and time to market.