translation VS http-kernel

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.

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: