You're mistaking HHVM with HPHPc.

They're both Facebook projects and one grew inspired by another, but they use different approaches.

It doesn't need to be written in a certain way, there may be new features in recent releases of PHP that don't work on HHVM but the HHVM folks are pretty quick to add in support for those features. Here is a little library[0] I wrote in PHP and this is tested on HHVM using Travis (see .travis.yml). I haven't had to write the PHP any differently, it just works (although it's an incredibly small library).

Edit: The speaker in the video also mentions that they have taken the test suites from the top twenty PHP projects and they test them against new releases of HHVM, further confirming that the syntax requires no special attention except for new language constructs.

[0] https://github.com/unfunco/bijective

It`s a jit-compiler for PHP. Code is compiled once to an intermediate representation (like Java) which makes execution faster on subsequent request.

Code does not have to be written in a certain way most of the time because hhvm is 98% compatible to all major PHP-Frameworks[1]. It also features a built-in webserver alltough static performance is lower than nginx.

[1] http://www.hhvm.com/blog/2813/we-are-the-98-5-and-the-16

No, it does not compile to C++, but to bytecode. HHVM's predecessor converted PHP to C++, though.

What's the difference between that and APC? The performance, or is there something else?

Confession: I haven't listened to the OP yet.

Somehow an asm.php