console VS http-kernel

Symfony console component. The Console component eases the creation of beautiful and testable command line interfaces.

I have to disagree. To me, declaring a method via the @method tag (in rare cases) is equivalent to actually declaring it in a class/interface. Due to PHP limitations, the obvious lack of generics, and what I wrote earlier, I simply couldn't do it any other way. Take eg. HttpClientInterface from symfony/http-client-contracts or InputInterface from symfony/console, they had different reasons but the outcome is the same.

I don't think so. Phoronix Test Suite is a big example. Plus, in the PHP community itself, there are so many CLI apps: Composer, PHPUnit, static analyzers like Phan, just to name a few. Symfony Console component has more than 9k stars, so this should mean PHP is a capable tool for CLI apps.

{ "name": "symfony/console", "version": "v4.4.8", "source": { "type": "git", "url": "https://github.com/symfony/console.git", "reference": "10bb3ee3c97308869d53b3e3d03f6ac23ff985f7" }, }

The compiling of the extension configurations is actually done in a compiler pass. This is called the Merge Pass and is the first compiler pass to be processed. Because of this, once our custom compiler pass reads the configuration of off the extension, we can be sure it is already compiled, cached and ready for use.

I present you the Symfony ControllerEvent, final class, no interface and a boatload of heavy dependencies.

In that regard, someone posted symfony's test suite as an example of good PHPUnit testing. The first file I clicked on demonstrated how worthless (IMO) unit testing can be: https://github.com/symfony/http-kernel/blob/v6.0.8/Tests/CacheClearer/ChainCacheClearerTest.php

The second one was in the Symfony HTTP kernel which is managed by Composer. That file contains this line:

You can also define routes in the method directly: