In reality, in Symfony you eventually put together the same stable projects each time, with the same implementation that you have experience with yourself and think it’s a good ‘plugin’.
The same applies to Laravel, only they by-default bolster a certain set of opinionated plugins, which means that those plugins have the necessary ‘exposure’ to remain actively maintained, and if this does not happen or one of those plugins nevertheless pull the plug, then you have 100% freedom to still take the Symfony approach and exchange the Laravel default implementation (by means of a “contract” / interface).
For example, it is perfectly possible to use Doctrine within Laravel, but the default is to use Eloquent, and most developers think this is fine, so this is not a popular choice.
The big difference with Symfony, however, is that Symfony is delivered more as a kind of DIY kit, where you have to assemble the kit every time you need something, which creates a kind of unrealistic feeling that there is more ” freedom” is compared to Laravel, while with Laravel you actually get the kit already pre-assembled in a certain color, a kind of “omakase”, so that you (IMO) can really start your project faster without loss of flexibility.
[Reactie gewijzigd door Arckedo op 15 februari 2023 00:07]
