My main worry with PHP is that its surface constantly grows. This means the language is
1. more complex to use (it took years for some parsers to implement the PHP 8.4 property hooks, and I suppose few people can explain how they work with inheritance and traits),
2. more costly to maintain (I remember when the developer of PHP's JIT left, the PHP foundation was worried because no one could understand the JIT code),
3. and has more security risks (critical security releases will continue).
I don't disagree with you, but the situation is more nuanced, and PHP's initial promises are now blurred.
> 1. A stateless functional core. It's cheap to run and quick to start.
Most modern codebases use a framework. And once you have to load Wordpress, Drupal, or even worse, Laravel, then it's no longer cheap and quick.
So PHP added several layers of complexity to mitigate this: an opcode cache, a code-preload system...
> 2. Every request has an environment created then torn down.
That's no longer always true. When the code preload is enabled, a request can leak into another.
> 3. Every request is single-threaded. [...] Async network/IO requests are handled via extensions.
You mixing up two different things. The default PHP SAPIs have single-threaded request handlers (though IIRC the default deploy stack of Laravel differs). But the language has a native async feature through Fibers, from which coroutines can be implemented (see amphp/amp).
So PHP on the server side is usually like JS on the client side (except for workers): single-threaded with async. Though I haven't seen much use of Fibers in the wild, it's in the language.