entwickler.com

Facebook schlägt Wellen. Nicht nur wegen verdächtigem Datensammeln und Auswerten, sondern auch mit dem Release von HipHop, dem intern entwickelten und jetzt der Öffentlichkeit vorgestelltem PHP-zu-C++-Cross-Compiler. Wir haben einige Stimmen gesammelt, dabei reicht das Spektrum von vorsichtiger Zurückhaltung bis hin zu ehrlich gelebter Begeisterung.

For now I think this is mainly interesting for "researchers" willing to work on improving the compatibility and more importantly the workflow around HipHop. I do not expect that anyone can really get a meaningful return on investment who makes this their business anytime soon [...]. Lukas Smith, 2010
aus: Short HipHop blurp

You might just have shifted your scaling problem. To determine the right scaling measures, a decent amount of thorough code profiling is required, and you might as well have to rethink your software architecture.

Turns out, you might have to walk a long road until you can even start to dance the HipHop. Stefan Priebsch, 2010
aus: Before you can dance

For all the benefits, there is a large group of PHP developers that won’t benefit: the average, every day developer. There are a vast number of websites that have a single server and not very much traffic; there are also lots of sites that run on shared hosts, or sites that have multiple sites on the same server. Since HipHop runs one web application at a time (with a built-in webserver), it’s impossible at the moment to run more than one website on a box. This is obviously less than optimal [...] Brandon Savage, 2010
aus: HipHop For PHP: Who Benefits, Who Doesn’t

[...] it is an incredibly impressive technical achievement that in the case of Facebook's use-case makes a lot of sense. It is just that 99.9% of PHP deployments out there do not share the same challenges as Facebook (massive, continually evolving code base and equally massive traffic), where the delivered performance increase would justify the HipHop's deployment and maintenance challenges. Ilia Alshanetsky, 2010
aus: My Thoughts on HipHop

HipHop has the potential to be an incredibly disruptive product in the PHP landscape. If your company runs a PHP application that requires more than two servers (you’ll want two just for redundancy), you have no reason not to explore using HipHop. Marco Tabini, 2010
aus: HipHop: What you need to know

[Absatz What HipHop means] If you do not have a separate development and deployment environment, don’t have a developer who knows C/C++, or use any PHP libraries where the source is not available (thankfully the encoded scripting market is small to non-existent in the PHP world), then the answer is nothing. You don’t have the development model that can support HipHop. Terry Chay, 2010
aus: Faster PHP fo shizzle—HipHop for PHP

HipHop also nur etwas für Profis am oberen Ende der Skala oder durchaus als schon ein tragfähiges Zukunftsmodell, das PHP auch aus Performance-Sicht auf ein Level mit Java & Co. stellt?