5 ms·
Four words : composer, symfony, laravel and php-fig. The php ecosystem is not what it was 4 years ago. Although due to backward compatibility the languages sti
by arkh 9y ago
Four words : composer, symfony, laravel and php-fig.
The php ecosystem is not what it was 4 years ago. Although due to backward compatibility the languages still has a lot of cruft. But this means old code often works directly with the last version and benefits from its performance improvement.
If your new project is about receiving an http request and send a response like a REST API I think it is a good tool for the job. If you want long lived process (kafka/rabbitmq consumers for example) or sockets it is possible to do it in php but you'll have a better experience with other stacks.
- bpicolo 9y agoThe kind of worn out ecosystem is my main dig with PHP. A couple parts of the ecosystem are outstanding, especially laravel, though laravel’s DId internals are a maze. (side note: Not a fan of DI being more or less required - it’s necessary for testing but the pattern is just a mess. Lack of static typing makes PHP kind of mediocre at DI, too) Outside of that there’s a ton of abandonware or just generally unmaintained libraries, though, and daemon/batch style processing is a tremendously common requirement that’s better served by other stacks.
- jrs95 9y agoHaving used both Laravel and Spring, I don't see Laravel being much worse at DI. Spring is just doing everything by Strings anyways, so if you're going to get failures they'll still be at runtime.
- bpicolo 9y agoSpring is certainly crazy with DI too. It's just rough to follow Laravel internals the times I've had to do it.
- porker 9y agoI don't get the love for Laravel. Things like validation, specifying validators in strings like it's 2003 grate with me. Symfony's a pain in the butt for over-engineering things (DataTransformers are a good place to start) but at least it's well thought through. What are the reasons to love Laravel?
- EdwinHoksberg 9y agoApparently the creater modeled it after Ruby on Rails, so I guess it's easier to use if you are used to that platform.
- subie 9y agoI found Validation a pain to use in Laravel as well which is why I don't use that feature. Everything else: MVC, Migrations, Blade, Auth, Email Handling, Artisan commands are why I keep using Laravel.
- vesak 9y ago> What are the reasons to love Laravel? Like you seem to have learned already, the reason to love Laravel is that it's not Symfony.