Laravel vs Symfony CRUD: Live-Coding Demo

For Laravel devs, a demo of creating (generating?) a simple Symfony CRUD, for comparison.

- - - - -
Support the channel by checking out my products:

- - - - -
Other places to follow:

[cardboarddignity]

I would like to see Symfony vids just to compare. I have worked with it just once and then that project switched to Yii2 (that also is Symfony-like). I kinda live the route schema there, the concept, but it lacks grouping and other stuff. For me, Laravel is much more developer friendly than any other

[JohnDoe-jcxp]

At first glance I like how routes are handled in Symfony.

[florianlutze]

I like how all properties of models are real properties in Symfony. I kind of miss that a lot in Laravel.

[oghenetegananu]

I love the fact that in symfony we have a command for creating crud.

I think this is something that I can contribute to laravel with help from senior devs like you

[JeffLewis]

Thanks for the video! I am currently debating a project and can't decide between Laravel and Symfony. I find Symfony more complex and a friend of mine swears by Symfony or Mezzio and claims Laravel is terrible. I'd love to see more Symfony videos.

[ayomidealase]

Nice, but i prefer laravel any day anytime

[nikolaystoychev]

Great video!
I welcome the idea of videos like this!
The comparisons between Laravel and Symfony really highlight the strengths of both frameworks. It's valuable to see different approaches, which gives us more ideas on how to improve our development process and create a better experience for developers. Having this kind of insight helps us make more informed decisions when building applications.
TNX

[vladislavkresta]

One thing I like better in Symfony than Laravel is how migrations are made. In Symfony, you have PHP properties with PHP attributes that say which column type, primary key, index, ... and migrations are created automatically by these attributes.
In Laravel, I have to edit my $fillable array, create migration, type in the change, ...

Like Povilas once said - you once create a migration file and never touch it again, but these database change mid work could be better handled in Laravel

[univiewee]

Yep, that would be good to see simple authentication, in order to compare to what we get with Laravel with couple of commands.

[AbdulRehman-mwsc]

It looks great, it would be great if you could share more videos comparing laravel stuff with Symfony, so we can have ground knowledge to easily shift for different projects from laravel to Symfony and from Symfony to laravel respectively.

Thank you for your efforts.

[isabelphillips]

Laravel any day, anytime 😍😍 ... I know there are some of Symfony's code in laravel but that is pretty much how close I can be to Symfony

[normanhuth]

I worked with both frameworks at my employers. (Symfony was used for all old projects and there are also Pimcore or Shopware projects).
New projects are set up with Laravel if a PHP framework is required.

The “Magic” is frowned upon by many. But with the right setup (PHPStorm, ide-helper, Larastan/PHPStan and Laravel Idea Plugin), working with it is no problem.

I like to read forums where many Laravel and Symfony developers talk to each other. Especially the counterarguments of Symfony developers against Laravel are often wrong or refer to very old versions.

The higher scalability of Symfony compared to Laravel is also often mentioned, which I personally cannot comprehend.
And “Laravel facades” are not facades in the sense of the facade design pattern. This is also often under criticism.

I wouldn't say that Symfony or Laravel is better.
But I find the development speed, community and the 1st party offer with Laravel very very very much better.

When it comes to the use of components, Symfony is clearly ahead, as these are also well documented for use outside the framework.
Which now prevents me from using Illuminate components. Especially for small console applications, I like to use illuminate/console for example.

[JeremyMoore]

I'm coming from Symfony to Laravel and these are some of the features I miss. So much quicker to get things running IMO

[Mohamed.G]

Nice video to have a look on symfomy framework
Thanks a lot

[matthiasbackhaus]

We use Laravel with Doctrine package instead of Eloquent in a very big project (100+ entities). There are pros and cons for me. I like separating entity and repository for bigger projects. We also build a smaller Filament app (bcs. of your channel btw), and here I like Eloquent more, it feels more fluent and easier considering no need for EntityManager.

[ahmadirfan]

The command console to make crud operation in Symfony is pretty similar to create scaffold in Ruby on Rails. That is what I see. But yeah, even though Symfony's code kinda bloated, quite long, and resources mixed together with controller, I guess it is worth to try..

[zoltalar]

Would be nice to see more Symfony videos

[shimadabr]

I find symfony much better to create more complex projects, since it follows a more "clean architecture" structure, so we don't need to constantly fight the framework when the project is not a simple CRUD. Specially for implementing DDD for example, I think we need to go against the "Laravel way" for a lot of things.

[richardwheatley]

Sylius in built on Symphony and it looks like a mature ecommerce solution.

[gizmoitus]

Nice review. I do want to address your issue with some of the "complexity" of the ORM. I don't think it is more complex, but it is different. Eloquent is an Active Record implementation, which is often criticized for not supporting single responsibility or separation of concerns. Doctrine is a Data Mapper ORM implementation. For that reason, Doctrine separates the management of ORM objects (the connections, transactions, etc) from the core mapping (the models) and from querying (the repository). Active Record is simpler, but that does not mean that it is better. Yes, people who are starting out find it easier to understand $user->save(). That doesn't mean that code is better. Having an entity manager is far more elegant, and downright wonderful to work with when you have multiple connections you are using, whereas (not picking on eloquent here) any active record ORM is quickly reduced to controller spaghetti at the point you start working with a lot of different objects and RDBMS transactions. In a simple example like this where you generate code, these things are created for you, even when you currently don't need them. Repositories have a variety of base methods available, but at that point that you want to add something customized, the structure is already there. Funny enough, I worked for a company that had a large direct to consumer service infrastructure written in Laravel, and the developers spent a lot of time essentially trying to add a repository layer on top of Eloquent.