Many web developers choose PHP frameworks because they are reliable and efficient. Although there are several PHP frameworks available, Laravel and...
For further actions, you may consider blocking this person and/or reporting abuse
I'm a Symfony developer and started to work recently on a big project in Laravel.
From my perspective, Laravel is more difficult to use than Symfony:
overloadfeature of Mockery, that opens an entire new set of problems)On the other side, Symfony:
overloadneeding: the code is clean and well writtenIn the end, I really don't like Laravel and its "simplicity": the simplicity is simply a set of bad practices that anyone who would like to learn how to structure code well should avoid (and will, once she/he knows what are antipatterns and which they are).
Thanks for sharing your view on this topic! Why do you think did the Laravel community become larger, dispite the cons you've mentioned?
Honestly? I have no idea: it is absolutely inexplicable to me...
We have to consider some things in how the two frameworks evolved over the years:
At start, Laravel didn't had all the components and features it now has, while Symfony was already a big framework with a lot of packages.
More, only in the last few years Symfony simplified a lot the use of the framework, specifically with the introduction of autowiring and autoconfiguration that made the injection of container useless (indeed, even an anti-pattern) and made defining and injecting services a piece of cake: it is sufficient to implement an interface (before attributes in PHP: now it is sufficient to add an attribute, without the need of an interface).
For me, now there is no reason to use Laravel instead of Symfony, mostly because it is common thought that for enterprise level projects, Symfony is better suited, while Laravel is better suited for MVP or small projects. I don't know if this is really true: I prefer, anyway, to start with Symfony, given I can arrange a small app or an MVP with just a few components (and, thanks to Flex, all is autoconfigured).
I know my point may be considered as the one of a "Symfony maximalist", but I'm seeing this point become real day by day, working with Laravel, without knowing nothing before about it, but knowing a lot about Symfony and the comparison, in my opinion, is in favor of Symfony.
Nice post!
Just a comment: Scalability is swapped at Summary section.
Laravel is the best
Why would you say so? :-) @amooxakermoud
I would choose Laravel only for POC or a project full of CRUDs. When it's come to business logic I prefer Symfony.
Can you explain why? @aswierc
Laravel does a lot of magic with its syntax (what can be considered as advantage for quickly done demo), symfony is better suited for large (more developers) project, easy to read by Java / .Net developer from my experience
oh this kind of click-bait articles :)
Seems like it worked in your case ;-)
exactly :D
Nice write up, thanks for sharing I was looking for this kind of updated comparison a month ago.
I think the scalability thing on the side of Symfony is a community myth. I personally feel Symfony is more Design Principles friendly to put in a way, let you set boundaries between code and framework easier to protect against changes.
But in practice it feels that more code is needed to accomplish the same thing.
Thanks for the feedback!
The performance benchmarks are out of date.
I'll check it, thanks for the feedback :)
Depend on your Familiarity!!!
True, but some Devs maybe still have the choice :)