Why Laravel/Symfony/etc if you can assemble your own “hodgepodge framework” from libraries?

Question

PHP

I ask you not to throw slippers, but to explain in simple words.

What is the advantage of all these frameworks (except for development speed), over, for example, the “hodgepodge framework”, where you can simply connect the same bramus router, database wrappers, validators, template engines, and other things that are convenient for developers to work with, and not what does the framework impose?

After all, they drag along a bunch of unnecessary things that are used extremely rarely, they impose their policy - this here, this there, it’s possible, it’s impossible.

As I understand it, a framework is just a universal tool (agreements??) so that when another developer opens the project, he understands what's what?

Answer 1

After all, they drag a bunch of unnecessary things with them.

delusion. Do not think that you are smarter than the collective brain of open source projects. Everything is needed there, and if you don’t need it specifically, then most likely because you haven’t read the docks and don’t know what opportunities this or that package provides.

they impose their own policy - this one here, this one there, so it is possible, so it is impossible.

not a policy, but a common architecture that has now become the de facto standard. Well, a bunch of syntactic sugar. There are no restrictions.

if you can assemble your “hodgepodge framework” from libraries?

will you assemble a good car from a hodgepodge of VAZ, BMW and Toyota parts? With a lot of experience with these machines - it is possible. Only this is Sisyphean labor.