Same here, I left PHP during the early 5.x releases. Unfortunately, I inherited some Symfony applications recently. Unfortunately, because the whole stack is terribly slow and held together by an insane amount of YAML and XML configuration files. Add "annotations" (that are parsed out of doc blocks and compiled into another bunch of PHP files) to the soup and party like it's 1998. That pile of classes you end up with will serve quite some traffic behind a good caching layer, typically in the shape of a well configured Varnish instance. Needless to say that runnig this on your own machine during development will not exactly give you the excitement of working on a fast, modern platform. Rest assured, "print_r() and die()" is still a thing.
Besides that, memory management is mediocre; just DON'T do long running processes with PHP. You want to enable a module? Good luck finding the right php.ini. Keeping a persistent connection pool to a database or similar is generally hard and intransparent, due to the fact that each instance serves exactly one request, but hey, at least PHP "automatically recovers" from errors...
Besides that, memory management is mediocre; just DON'T do long running processes with PHP. You want to enable a module? Good luck finding the right php.ini. Keeping a persistent connection pool to a database or similar is generally hard and intransparent, due to the fact that each instance serves exactly one request, but hey, at least PHP "automatically recovers" from errors...
I left for good.