On 4/19/2016 6:54 PM, David Zuelke wrote: > I think this solution is merely a band-aid for a more profound architectural > weakness of current PHP setups, where a web server call out to the engine > (via embedding or FastCGI) to execute a script, which causes this recurring > initialization overhead in the first place. > > The future is (or should be) servers implemented fully in PHP code (e.g. > PHP-PM), just like every other comparable language (Ruby, Python, Java, ...) > already does. That also brings many other benefits, such as the ability to > handle upgrades to WebSockets in the same codebase, stream request bodies as > they're being uploaded, and so forth. > > And the performance figures that PHP-PM delivers with Symfony validate that > approach IMO. >
This requires proper memory management, no matter how: https://software-gunslinger.tumblr.com/post/47131406821/php-is-meant-to-die https://software-gunslinger.tumblr.com/post/48215406921/php-is-meant-to-die-continued -- Richard "Fleshgrinder" Fussenegger
signature.asc
Description: OpenPGP digital signature
