Every non-trivial web app I've ever worked with has tons of persistent state. DB connection pools. Translations. Configuration. Recreating that on every request is just wasteful.
Have you measured the overhead and impact on performance compared to other development stacks?
As for the other stacks: I do what everyone says not to do. I write stateful servers in native compiled languages with no GC. So far I've yet to encounter any scalability problems. They simply do not exist when said servers are runninig on 32 core monsters with gobbles of RAM and not slowed down by interpreters, garage collection and bazillion of abstraction layers. Sure I could not serve Facebook using this, but hey it works just fine for the 90% of the rest and that is where I make my money ;)
But it also has some security benefits - with that model it’s harder to have exploits (as in your request you don’t carry over any other state), session swaps, no need to care about concurrency, locks, etc.
It’s by accident, but it’s a real benefit of php.
The PHP community's track record on security is abysmal compared to all those other environments that don't throw away the world.
I can have a car with super safe airbags, that does horrible in crash tests. That doesn’t make those airbags bad.
Luckily PHP is very damn fast so you don't see it often, but you'll start questioning the whole industry if you are hired as consultant into many middle-to-large-sized projects and see the hacks people have come up with.
pm2 with ts-node is the best I can achieve so far but not fast enough not to hold for a second.