Live data from Hacker News

Facebook Porting PHP To JVM

nerds-central.blogspot.com

11–20 of 68 posts

Re: Facebook Porting PHP To JVM

#11
post #5
post #3

Earlier quoted context omitted.

No reason it should take that long. The article suggest 6 person years - which could mean 6 people for 1 year.

Just like nine women can have a baby in one month?

exactly. One makes the head, two make each arm, etc...

of course, you can't do that with computer software

Re: Facebook Porting PHP To JVM

#13
post #9

I guess someone must really love PHP, though I'm slightly confused as to why. If you're going to make such a massive undertaking anyway (it's not just the new runtime, all existing code will have to be re-tested and re-debugged), why not sink the man-hours into putting it into a new language better suited to the task from the start?

This is where someone posts the Joel on Software link about Netscape (I'm on my iPhone else I would).

Also, developing a new implementation of PHP allows site development to continue in the meantime.

Re: Facebook Porting PHP To JVM

#14

Why do these companies like the JVM so much? Twitter, and now Facebook. Does it have that great of performance?

Yes. http://shootout.alioth.debian.org/u64q/which-programming-lan...

Note that Java compares very favorably with C. (Of course, the real thing to take away from that chart is: why don't all the JVM users switch to Haskell? It's more concise, safer, and has a better community.)

Re: Facebook Porting PHP To JVM

#15
post #3

It's the summer of 2018. Facebook shares drop to 17 cents as their PHP to ASM compiler project nears completion.

No reason it should take that long. The article suggest 6 person years - which could mean 6 people for 1 year.

try reading The Mythical Man Month http://en.wikipedia.org/wiki/The_Mythical_Man-Month

unfortunately my boss thinks as you do..

Re: Facebook Porting PHP To JVM

#16
post #9

I guess someone must really love PHP, though I'm slightly confused as to why. If you're going to make such a massive undertaking anyway (it's not just the new runtime, all existing code will have to be re-tested and re-debugged), why not sink the man-hours into putting it into a new language better suited to the task from the start?

Because there are millions of man hours of PHP from FB and it will cost less than one hundred thousand to port that work to the JVM.

Yes the code will have to retested, but if you rewrite then you rewrite AND retest. Working code makes a great test suite, something you lose in a rewrite.

Re: Facebook Porting PHP To JVM

#17

Why do these companies like the JVM so much? Twitter, and now Facebook. Does it have that great of performance?

There aren't that many problems with the JVM compared with Java. Most of what makes java suck is the language and what makes the performance sluggish is the standard lib as well as the programming style the community encourages.

As much as I love to rag on java the language the JVM is generally a solid piece of work that makes reasonable tradeoffs.

Re: Facebook Porting PHP To JVM

#18
post #3

Earlier quoted context omitted.

No reason it should take that long. The article suggest 6 person years - which could mean 6 people for 1 year.

try reading The Mythical Man Month http://en.wikipedia.org/wiki/The_Mythical_Man-Month unfortunately my boss thinks as you do..

You either never read the book or are interpreting it wrong.

The premise is that as you add more people to an EXISTING project, the amount of time it will take to complete will increase. However, if all of those people are involved from the beginning, then you are not subject to the same phenomenon - within reason of course.

So while it might not be "6" developers working on it for a year, it could potentially be 9 very devoted developers cranking this out with good results towards the end of the year.

Re: Facebook Porting PHP To JVM

#20
At this point I have to just laugh. They literally already paid for the development of a prototype for a faster PHP, and decided not to pursue that route: http://morepypy.blogspot.com/2012/07/hello-everyone.html. I have to assume they have some insane internal politics, because there's no sane technical reason to develop HipHop (static subset-of-php to C++ compiler), then start the HipHop VM, then fund the PHP on PyPy prototype, and now apparently move to a PHP on the JVM.
Post reply on HN