[psychoslave]

Did also plaid with Ruby on Rails, or even Sinatra, and how would your rank the dev XP compared to Laravel?

[midrus]

I did use Rails for several months while helping a friend with his business/sideproject/startup kick-off and despite I really liked it, I much prefer Laravel + Livewire and PHP (https://tallstack.dev/) over Rails + Hotwire + Ruby, but it's up to personal preferences:

- I prefer things to be more explicit than implicit and lean more towards configuration over convention.

- I lean more towards having types/typing information than not having it

- PHP is way, way, way more used than Ruby

- Performance (just talking about development environment performance) is a lot better in PHP (no server restarts, etc)

- Availability of third party libraries is a lot stronger on the PHP side, probably due to it being more popular

- Tooling and editor support. This is a big one for me, and I've found out things to work a lot better with VSCode for PHP than for Ruby. Probably related to it being both, more popular and more explicit.

- Overall, Laravel feels even more complete than Rails and just fits better my brain.

But, I think Rails is still great, and I would use it over building a microservices mesh of Go servers on kubernetes with React frontends, etc, etc.

[cutler]

I'll take Rails over Laravel any day. Verbose, doc-block-riddled, pseudo-Java PHP is the polar opposite of elegant, composable Ruby.

[midrus]

Well, probably you are right, but for me ecosystem, libraries, tooling, editor support, performance, etc is far more important than language syntax. But we all have our preferences and that's ok.