| I started making stuff in rails around 2013, got a job at a PHP firm around 2018 where I've worked with a lot of Laravel. At this point i know Laravel better than rails, I would say. Most of the things you mentioned is either present in rails by default, such as queues and cache. Yes, you have to install external dependencies such as device for authentication etc, but that takes mere seconds to set up. Like, two or three CLI commands and you're done. Rails has "liveview" too in the form of Stimulus. Never heard of filament tho, looks kinda neat. I know there are some similar gems for rails, but I have little experience with these kinds of products. I still pick rails for my private development projects. Laravel and Rails both have their upsides, but none of them are really a game changer enough that I'dd consider dropping rails in favor of Laravel. Some of the things I like with rails in particular are things like * Interactive repl on exception screens in the browser. I can interrogate the state of my request when the error occurred. * "Intellisense" in the rails console(and also interactive repl) is kinda nice. * I find it easier to configure and setup rails in docker than php. * I like that in rails validations are defined on the model and not on the request. * I like the built in form_for, form builder in rails, i like that its also very extendable. Which makes it easy to make reusable components with little to no code. * My IntelliJ is often much better at understanding and parsing my rails projects than my rails projects. * Lots of small rails things such as route functions instead of the route helper. * It feels to me like rails has less boilerplate and is better at generating scaffolds, but that might be because of the laravel code I have been working on. |