Facebook Moving To The JVM

&#62; ...their interest in implementing PHP using invoke-dynamic on the JVM<p>This is very interesting.<p>&#62; The main seismic event will be nothing less than the complete removal of interpretors from main stream general purpose programming.<p>This is hyperbolic drivel.

Makes sense - the JVM is fast and stable. It comes with a huge array of tooling and its own built in debugging system. It is well supported and cross platform. Why would you not want to take advantage of all that good stuff?

Source? Or anything to show that this should be trusted?<p>And even if the post is correct and they actually are testing out an run-php-on-the-jvm solution, it's not the same as moving all their stuff onto it.

There is already a PHP for JVM:<p><a href="http://www.caucho.com/resin-3.1/doc/quercus.xtp" rel="nofollow">http://www.caucho.com/resin-3.1/doc/quercus.xtp</a>

Wouldn't facebook benefit from just starting to rewrite parts of their infrastructure in a language more suited to their scale, like twitter did with scala? I can't help but feel all this effort into bending php into corners it was never meant for is not helping them in the long run.

PHP is fine and dandy for Wordpress sites but to think that Facebook got this far on it is nothing short of amazing.<p>If this article proves true it'll be a good move for them.

Will Facebook contribute to Quercus, or doing their own thing? <a href="http://quercus.caucho.com/" rel="nofollow">http://quercus.caucho.com/</a>

As I said only yesterday[1] there is <i>no solid evidence that this is happening</i>.<p>None.<p>This is, at best, a tertiary source.<p>[1]: <a href="http://news.ycombinator.com/item?id=4374216" rel="nofollow">http://news.ycombinator.com/item?id=4374216</a>

first twitter, now facebook.