translation VS console

I'm wondering if you system means you need 100 database round trips every time you display a page with 100 localised strings. But to cope with everything else I'd suggest a third-party library. PHP itself doesn't have anything too fancy (gettext gets the job done, it hasn't received significant updates in years, there's a good third-party toolset). I'm not versed enough in i18n libraries as to recommend one but I know there're Symfony Translation and Laravel Localization.

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" }, }