Both have ecosystems and expected standards - basically a philosophy.
However, to keep this simple (and from my perspective), the key differences that I've noticed over the years:
Laravel:
Used by a lot of companies in the US.
Has amazing marketing and community support.
Has a huge toolset and this architecture is expected to be used.
Laravel libraries are Laravel packages only (developer(s) will need to make non-laravel specific version).
Projects are easily bootstrapped and can be deployed quickly (only if the developer knows the framework and its tools).
Symfony:
Used by a lot of companies in Europe (especially in France)
Has very little to no marketing, has a community but only focused on the Symfony 'Core' Bundles and documentation.
Follows domain-driven specific code standards and allows full flexibility.
Symfony libraries are not specific to bundles, therefore they are universal and are standalone libraries (that can be used in any project including Laravel).
Projects can go deeply into specific company/business requirements.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Both have ecosystems and expected standards - basically a philosophy.
However, to keep this simple (and from my perspective), the key differences that I've noticed over the years:
Laravel:
Symfony: