3 ms·
I have trouble believing that "no shared state" and "reloading your code with every execution" can possibly be an advantage in production. Maybe when you're de
by puls 16y ago
I have trouble believing that "no shared state" and "reloading your code with every execution" can possibly be an advantage in production.
Maybe when you're developing, sure, but they otherwise only force you in to inefficient workarounds.
Of course, the statelessness of HTTP contributes to the necessity, but using a proper language (there, I said it) doesn't get in the way of creating a proper server application.
- foobarbazetc 16y agoThe best thing about PHP is that the entire 'world' for each script is torn down after every request. Pair that up with APC in apc.stat=0 mode, and you have the easiest deployment method for a production site anywhere. The worst thing about PHP is that it's PHP.
- old_sound 16y agoIt depends on the size of your project of course… But if you don't want to reload and compile the scripts for every request, then you use APC as other commenter posts here. My main problem with that way of PHP working is that you have to load again and again all the configuration, even if say your database is still on the same host:port. With a long running process, you'll just load that once. For me it always depends on the task at hand what tool you'll use.