rfc VS Symfony

That said, I do agree with the general opinion that you should stay clear. Now even more so than in the past. I'm saying this as someone who has been using Joomla for well over 10 years and contributing for some years as well. Although Joomla has some big plans ahead (https://github.com/joomla/rfc), I don't expect it to get far. Joomla has a long history of bad practices and incompetent maintainers and this has gotten worse in the last few years. While there are a few high level developers somewhere behind closed doors, the majority of maintainers don't even know PHP basics, do not follow PHP development, do not care to review the submitted code properly, do not care to look into reported issues. Yes, unit tests are very limited and human tests are borderline useless in most cases. Not to mention that every other patch release intentionally introduces B/C breaks despite the project promising Semantic Versioning.

Let's have a look at the class EventSourceHttpClient and try to use it in Symfony\Component\Webhook\Server\Transport. It's an entirely hypothetical example to illustrate the point.

Symfony is an open-source PHP framework developed by SensioLabs which has a thriving community of over 300,000 developers with 29k stars and 9.4k forks on GitHub. It provides a set of reusable PHP components and a development methodology for building complex and scalable web applications. It is recommended due to its advanced features and user-friendly environment. The user can also develop microservices.

Symfony 7

Would be great to see for https://github.com/symfony/symfony, thanks! As that's a monorepo it may provide a challenge to the tool.

As Shopware is mostly based on the Symfony framework, which is in turn based on the PHP language, we should also consider learning about the basics, which will also be useful for other frameworks apart from Shopware, like Symfonycasts, symfony.com, php.net.

Use PHP frameworks such as Symfony. It cares about all the stuff.

Symfony is a PHP framework. https://symfony.com/

It caused much of the internal of Drupal to be re-written. This included how it was extended. With previous major versions you learned about new features and APIs. They followed mostly existing design patterns so it was easy to learn and updates your extensions for. With Symfony you had to learn whole new systems and ways of doing things. It was like learning something entirely new. And, porting extensions to it was far more work and time.

Also, the updates made Drupal slower while consuming far more system resources for the same thing. This increased costs to operate.

Internally, the kernel executes a controller, that is a callable, passing it an array of arguments. For each of these arguments, Symfony calculates its value using services that implement the ValueResolverInterface1.

Drupal is one of the content management systems aka CMS. It has long history and good stability, which is based on PHP and Symfony.