phphhvm_PHP6中的HHVM与ZendEngine

php hhvm

The fabled PHP 6 is long overdue. This unicorn of the web dev world has been “coming” for decades now, and it’s still not clear whether or not it’s actually something that’s going to happen in this decade, or just an idea, a fantasy of the PHP userbase. Minor versions like 5.4 > 5.5 and 5.5 > 5.6 bring so many new features these days anyway, we often see them as major versions.

传说中PHP 6早该发布了。 这个Web开发界的独角兽已经“出现”了几十年了&＃xff0c;目前尚不清楚这是否是这十年中将要发生的事情&＃xff0c;或者只是一个想法&＃xff0c;一个PHP用户群的幻想。 无论如何&＃xff0c;次要版本5.4> 5.5和5.5> 5.6如今都带来了许多新功能 &＃xff0c;我们经常将它们视为主要版本。

My own personal fantasy for v6 is function naming consistency, a total break of backwards compatibility with PHP <6 in terms of global namespace pollution, and a full rewrite of all data types to classes much like in Scala or Dart, but hey, we all have our wild dreams.

我对v6的个人幻想是函数命名一致性&＃xff0c;就全局命名空间污染而言完全中断了与PHP <6的向后兼容性&＃xff0c;并将所有数据类型完全重写为类似于Scala或Dart的类&＃xff0c;但是&＃xff0c;嘿&＃xff0c;我们都有我们疯狂的梦想。

For a great article on the unfortunate fate of PHP 6, please see here – and make sure you don’t skip the comments. There are some valuable lessons about the attitudes of core PHP devs to be learned there.

要获得有关PHP 6不幸命运的精彩文章&＃xff0c;请在此处查看 -并确保不要跳过注释。 关于核心PHP开发人员的态度&＃xff0c;这里有一些有价值的经验教训。

前提 (The premise)

Not many people know this, but http://www.phpclasses.org has some interesting, if very awkward podcasts rather often. It’s sometimes difficult to weed out the useful information from these talks, but Manuel’s contents list usually helps. If you’re curious about changes in PHP and keeping up with the latest news, why not fire it up while exercising, coding, cooking or whatever else? In the latest edition between Manuel Lemos and César Rodas, an interesting topic arose among others – Facebook’s HHVM replacing Zend Engine in PHP 6.

没有多少人知道这一点&＃xff0c;但是http://www.phpclasses.org经常会播出一些有趣的(即使很尴尬的)播客。 有时很难从这些谈话中剔除有用的信息&＃xff0c;但是曼努埃尔的内容清单通常会有所帮助。 如果您对PHP的更改感到好奇并紧跟最新消息&＃xff0c;为什么不在锻炼&＃xff0c;编码&＃xff0c;烹饪或其他任何事情时就将其启动&＃xff1f; 在Manuel Lemos和CésarRodas之间的最新版本中 &＃xff0c;出现了一个有趣的话题– Facebook的HHVM取代了PHP 6中的Zend Engine。

While this was purely speculation on the part of the participants, and whether or not you believe in PHP 6, you have to admit it’s an interesting notion. As we’ve seen in the HHVM article, and on the HHVM blog, HHVM has been making strides in becoming compatible with most of the popular libraries, CMS, and frameworks out there. The team is doing what it can to improve performance as much as possible while keeping it compatible with existing codebases for various products. Let’s entertain the possibility of HHVM replacing ZE in PHP 6 and look at the pros and cons.

尽管这纯粹是参与者的猜测&＃xff0c;以及您是否相信PHP 6&＃xff0c;但您必须承认这是一个有趣的概念。 正如我们在HHVM文章和HHVM博客中所看到的那样&＃xff0c;HHVM在与大多数流行的库&＃xff0c;CMS和框架兼容方面取得了长足的进步。 该团队正在尽最大努力提高性能&＃xff0c;同时使其与各种产品的现有代码库兼容。 让我们来探讨一下HHVM在PHP 6中替换ZE的可能性&＃xff0c;并探讨其优缺点。

优点 (The pros)

Obviously, performance. HHVM is leaps and bounds faster than vanilla PHP, even with the default built in OpCache in 5.5. It uses fewer resources to do things faster. One can’t not see the advantages of this – consider, if you will, just the savings on cloud deployment bills. Fewer CPU and RAM usage means fewer instance hours.

显然&＃xff0c;性能。 即使使用5.5中内置的默认存储&＃xff0c;HHVM的速度也比普通PHP快得多。 它使用更少的资源来更快地处理事务。 谁也看不到这样做的好处–如果可以的话&＃xff0c;只需考虑节省云部署费用即可。 更少的CPU和RAM使用量意味着更少的实例时间。

The next advantage is HHVM being backed by Facebook. Facebook uses HHVM to deploy their own PHP code, so they need to make sure it’s as efficient as possible. A 1% CPU spike means tens of thousands of dollars in expenses for them, so it’s only natural they’d rather throw that money at the HHVM team to make sure it never happens. As a result, HHVM is being developed by people far more experienced and focused – especially in today’s high-concurrency high-traffic world – than the actual core developers of Zend Engine and PHP. As an example, consider the fact that Facebook had generators in PHP three years before they made it into the mainstream PHP release.

下一个优势是Facebook支持HHVM。 Facebook使用HHVM部署自己PHP代码&＃xff0c;因此他们需要确保它尽可能高效。 1&＃xff05;的CPU高峰对他们来说意味着数万美元的支出&＃xff0c;因此&＃xff0c;他们自然愿意将这笔钱扔给HHVM团队以确保永远不会发生&＃xff0c;这是很自然的。 因此&＃xff0c;与Zend Engine和PHP的实际核心开发人员相比&＃xff0c;HHVM的开发人员更为经验丰富且专注(尤其是在当今高并发&＃xff0c;高流量的世界中)。 例如&＃xff0c;考虑一下Facebook在使用PHP生成器三年后才成为主流PHP版本这一事实。

A further advantage is the ability to statically type in the most recent version of HHVM, via their internally developed Hack “language”. Hack is a derivate of PHP, but supports static typing. You start files you want to type check before compilation with instead of , and the compiler does the rest. A more detailed article on Hack is in the works and will be published soon. This approach further increases the quality of compilation, making native code that much more efficient, and HHVM’s PHP that much faster.