upvote
> once you have to load Wordpress, Drupal, or even worse, Laravel, then it's no longer cheap and quick

The frameworks aren't slow: https://tideways.com/profiler/blog/php-benchmarks-8.6-vs-8.5...

reply
From your own source, a basic demo with Laravel peaks at 95 requests/s/core. It's worse with Wordpress at less than 20 r/s/core. That's slow.

The last round of TechEmpower web benchmarks computed the framework overhead. Depending on the task, the performance of Laravel was 5% to 20% of the native PHP code, i.e. 5 to 20 times slower. Source : https://www.techempower.com/benchmarks/#section=data-r23&tes...

reply
It would be nice if you could request that unused parts be disabled. Maybe in the first line of your file.
reply
> That's no longer always true. When the code preload is enabled, a request can leak into another.

That's in the same bucket (to me) as, say, L1/2/3 cache leaking between CPU threads. That's resulted in real attacks but it's not really the fault of my programming. I would rather the bug be in the language or the compiler/interpreter or even the framework because it's more likely to get found and fixed than if it was only code written by me for me.

As an aside, PHP eliminates a whole class of bugs that don't exist in, say, C/C++ eg string buffer overflows. Yes, the PHP engine can itself have buffer overflows but as per my previous point I trust the library developers and the volume of people who use and analyze it more than being totally correct with my own string handling.

> But the language has a native async feature through Fibers, from which coroutines can be implemented (see amphp/amp).

Only a single fiber runs your PHP request at any one time. This still fits the same model.

reply