console VS fig-standards

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 namespaces and class names must follow this example.

I would familiarize yourself with the following PHP standards: https://www.php-fig.org

The PHP Standard Recommendation, or PSR for short, from the aforementioned PHP-FIG.

That's what happens if you use a PSR-4 autoloader and not utilise PSR-4 in your project structure 👀 So either use PSR-0 or properly use PSR-4.

PHP really "got it's act together" in my view when packagist and composer (which are PHP's equivalent of npm) became mainstream and with the release of the PSR community standards. We were admittedly a little behind the curve with regards to package managers but with standardised formats and not having to copy and paste zip file libraries anymore, PHP received a new lease of life.