What are the _essential_ (practically significant) differences between Symfony and Laravel?

Question

symfony

Hello.
Over the past couple of months, I got to know Laravel a little - everything seems to be cool, but there are few ready-made solutions that are actively supported by developers. Well, you know, I want something like phpBB3 with Laravel under the hood :D And so that there are a lot of such projects and different directions. And now I need to make a community site, and so far I have not found a suitable ready-made open source engine for this based on Laravel.
In this regard, I thought: maybe the situation is better in Symfony? Based on it, the new Drupal plows, maybe there is something else ...
But I am not at all familiar with Symfony. And a related question:

- And what are the SIGNIFICANT differences between Laravel and Symfony?

Let me explain:
Blade vs Twig && Eloquent vs Doctrine, as I believe, this does not count - the same is only in profile (this is with a cursory acquaintance).
What is really significant?
I liked the freedom in Laravel - that is, if I wish, I can easily cram PHP code into templates and RAW-SQL into queries to the database and cram these queries even into the router)))) and everything will work.
Is it true that this will not work in Symfony?
Thank you.

Answer 1

The difference is in the scope of these frameworks. On Laravel, you can write a project faster, which is important for startups (people call this approach "on the knee" or "**** **** and in production"). And on Symfony it is more supported, which is important for corporate development.

Answer 2

Eloquent = Doctrine?)
I advise you to understand at least a little what it is, and what patterns are implemented in the Doctrine, and which in the eloquent.

I liked the freedom in Laravel - that is, if I wish, I can easily cram PHP code into templates and RAW-SQL into queries to the database and cram these queries even into the router))))

Write on anything, anyway, it will go to the trash, because no one will support it.
You don't need a framework for what you want to do.
Again - you don't need a framework. A framework is a framework for an application that you will write.
You have heard enough somewhere about frameworks, and now you are trying to talk about them without even understanding what they are and what they are for.
You need a ready-made constructor / CMS

Answer 3

You will get everything. You can hammer nails with a microscope if you wish. I once came to a project that was deadlocked by a talented programmer from India. He created a huge twig extension from which he directly made requests to the database. When a page was loaded using this extension-a, then 800 kopecks of identical requests went to the database. Those. With a fool, you can break anything.

Answer 4

Perhaps you should first understand what a framework is and what is the fee for using it. There is no silver bullet, just like there is no perfect framework. Laravel is a popular framework with a lower entry threshold than Symphony, which is suitable for people who understand what and why they write. No framework forgives mistakes, but symphony does not allow you to do some bad things from the very beginning. The price to pay for this is its high entry threshold. In general, I advise you to look at other frameworks, try them and decide what you really like. I once came to Yii and write most of the projects on it, although I also use symphony from time to time.