Interesting that people keep coming back to this issue of PHP on the JVM: project zero, quercus, and likely others. As someone who works in both PHP and Java,

Interesting that people keep coming back to this issue of PHP on the JVM: project zero, quercus, and likely others. As someone who works in both PHP and Java, I see pros in both (and cons, of course). The couple of comments in the OP post makes me think he doesn't really 'get' PHP's strengths for what they are. "You still can emulate the zend php working mode, when each request executes inside isolated environment + hot-reload" No, it's not 'hot reload' - it's not even 'reload'. It's just 'load', because everything is gone at the end of the request (yes, you could call it reloading, but it's not reloading and replacing an existing internal thing, because that thing is gone). Rethinking this... yeah, I know why some people use the term, and 'hot reloading' in Java is a 'thing', it ticks me off a bit that people push Java-land mentalities in to PHP to 'fix' things that aren't problems (and yes, there's plenty of problems with PHP, as with almost any language). "You don’t need Apache or Ngnix to implement web apps on JPHP" Technically you don't need to for PHP either - there's been a built-in web server for a few versions now, but... it's not marked for production. Given how many people put up nginx or apache front-ends on Java app servers... this doesn't seem to be an issue so much as a benefit - front-end caching/proxy servers provide more benefit than just serving the app directly.