Now I'm going to have to go and read the article again. The understanding I got was that HipHop was a JIT technology, where the PHP would be the deployed object and it would be translated/compiled when first hit.
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Tuesday, February 09, 2010 12:18 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] HipHop for PHP
I didn't mean to imply that Facebook is programmed in C - sorry about that. I gathered that they used both PHP developers, and C developers. The former would develop and test new functionality, while the latter would transform the PHP into C as part of the process of moving it into production. It wasn't clear to me how automated the transformation process was.
So that begs the question, will Facebook become a supplier of transformation and runtime tools for PHP?
-Nathan.
----- Original Message ----
From: "MattLavinder@xxxxxxxxxxxxxxxxxxx" <MattLavinder@xxxxxxxxxxxxxxxxxxx>
To: Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
Sent: Tue, February 9, 2010 9:29:02 AM
Subject: Re: [WEB400] HipHop for PHP
You are essentially right but your description implies Facebook is now
programmed in C, which I is inaccurate. Based on what I read, the C code
generated is not maintained. It is simply an intermediate step that is
used to create a compiled binary. PHP code is the only thing modified and
maintained by Facebook engineers. Think EGL. It generates the Java or
Cobol code but you (are supposed to) only maintain the EGL code. So this
all happens seamlessly with little to no PHP code modification (They admit
eval doesn't work- but that is avoided by most PHP programmers).
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Nathan Andelin <nandelin@xxxxxxxxx> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|02/09/2010 10:49 AM |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Re: [WEB400] HipHop for PHP |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
From: Aaron Bartell
I would say that FaceBook couldn't run on the PHP of 6
years ago without having an incredibly huge server farm.
The facilitator at the conference where HipHop was presented indicated that
FaceBook had "tens of thousands of web servers". It was an off the cuff
remark. Did anyone else catch that?
It's actually not clear to me what HipHop is. It sounded like they
transformed their PHP code into C, and compiled it. And rewrote the PHP
runtime engine to evoke it. So that Facebook is essentially a C
application. Is that right?
-Nathan.
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/web400..
midrange.com
