php swoole 未来_未来PHP

php swoole 未来

As developers, we find ourselves living in exciting times. With increasing attention paid to online activities, we’re working with larger data sets (even “big data”); scalability and connectivity are more important than ever before; the very nature of privacy is being re-examined. But quietly, in the shadow of all of this, sits perhaps a more pragmatic question. How will PHP change and grow to enable us to build the future, whatever it may hold?

作为开发人员，我们发现自己生活在令人兴奋的时代。 随着人们对在线活动的日益关注，我们正在处理更大的数据集(甚至是“大数据”)； 可扩展性和连接性比以往任何时候都重要。 隐私的本质正在重新审视。 但是，在所有这些情况的阴影下，悄无声息地提出了一个更为务实的问题。 PHP将如何变化和发展，以使我们能够构建未来，无论未来如何发展？

我预言 (I Predict)

Will the inconsistent string function signatures ever be normalize? I doubt it. Will PHP ever be multi-threaded? Probably not, but maybe we’ll see Promises or Lua-style coroutines. If a police box suddenly appeared and an eccentric man popped his head out and said, “Behold, I bring you a PHP from the future!”, what might we see? I predict:

不一致的字符串函数签名会被归一化吗？ 我对此表示怀疑。 PHP会成为多线程吗？ 可能没有，但也许我们会看到Promises或Lua式的协程 。 如果突然出现一个警察亭 ，一个古怪的男人突然抬起头说：“看，我带了一个来自未来PHP！”，我们会看到什么？ 我预言：

• We’ll see a version of PHP with a double-digit minor version number. It would be wonderful to have full native support for working with Unicode-encoded strings, but the dev team has all but given up on it so don’t hold your breath. With no clear changes intrusive enough to warrant a major version bump, I can easily imagine a PHP 5.10, 5.11, 5.12, …

  我们将看到带有两位数的次要版本号PHP版本。 对于使用Unicode编码的字符串提供完全的本机支持将是很棒的，但是开发团队几乎已经放弃了它，因此请不要屏息。 没有明显的变化足以引起主要版本颠簸，我可以轻松想象出PHP 5.10、5.11、5.12，……

• We’ll see minor enhancements that mirror other programming languages. We’ve recently gained binary number literals, short array syntax, and function array referencing in PHP 5.4, and generators and finally in 5.5. Python-style array slicing would be welcome, as well as a C#-inspired get/set property syntax.

  我们将看到反映其他编程语言的较小增强。 最近，我们在PHP 5.4 ，生成器以及finally在5.5中获得了二进制数文字，短数组语法和函数数组引用。 欢迎使用Python样式的数组切片，以及受C＃启发的get / set属性语法 。

• The ecosystem will have less frameworks, more meta-frameworks. First there were libraries, then CMS and blogging platforms, then full-featured frameworks. The monolith platform trend has peaked and we’re scaling back with micro-frameworks and meta-frameworks. Light-weight platforms that gather diverse libraries into an easily-installable bundle or package will bring us full-circle.

  生态系统将拥有更少的框架，更多的元框架。 首先是图书馆，然后是CMS和博客平台，然后是功能齐全的框架。 整体平台的趋势已经达到顶峰，我们正在通过微框架和元框架进行缩减。 轻量级平台将各种库收集到易于安装的捆绑包或软件包中，将带给我们全方位的支持。

• There will be a plethora of new extensions. New tools like Zephir make it easier for non-C developers to write extensions, so expect to see a fair amount of new extensions as these offerings mature. And of course, some extensions now in Pecl may make it to core and old extensions will be retired. embedded NoSQL service would compliment the SQLite extension nicely, don’t you think?

  将会有大量的新扩展。 Zephir等新工具使非C开发人员更容易编写扩展，因此随着这些产品的成熟，期望看到大量新扩展。 当然，现在Pecl中的某些扩展可能会扩展到核心，旧的扩展将被淘汰。 嵌入式NoSQL服务会很好地补充SQLite扩展，您不觉得吗？

• There will be less reliance on the Zend Engine. Most people aren’t aware of other implementations of PHP, such as Phalanger, Quercus, HHVM, and even Parrot. A future where various run-times, each optimized for a particular use case, can be swapped out as needed doesn’t seem implausible.

  对Zend Engine的依赖将减少。 大多数人不了解PHP的其他实现，例如Phalanger ， Quercus ， HHVM甚至Parrot 。 将来可以根据需要交换各种针对特定用例进行了优化的运行时， 这似乎并不令人难以置信 。

• PHP will adapt. An increasing share of mobile devices, C10k, Web Sockets — yes, the way we use the Web is changing. Offerings like FastCGI/FPM, HHVM, and Ratchet are just the tip of the iceberg of what PHP needs to meet these challenges head-on. But we might find PHP in unexpected places, too. How about in routers, smart appliances, and other devices? With a built-in web server and embedded database, the *AMP stack can now be spelled just PHP. Shipping a release with a reduced set of core extensions/functions and specialized run-time could make Embedded PHP a reality.

  PHP将适应。 越来越多的移动设备( C10k和Web套接字)所占份额-是的，我们使用Web的方式正在发生变化。 FastCGI / FPM ，HHVM和Ratchet之类的产品只是PHP迎接这些挑战所需要的冰山一角。 但是我们也可能在意想不到的地方找到PHP。 在路由器，智能设备和其他设备中如何？ 使用内置的Web服务器和嵌入式数据库，* AMP堆栈现在可以仅拼写为PHP 。 发行具有减少的核心扩展/功能集和特殊运行时的发行版可以使Embedded PHP成为现实。

• PHP will thrive. Despite its warts, there aren’t any mainstream languages that come remotely close to integrating with the web stack as intimately and as flexible as PHP does. We can access incoming data directly with $_GET and $_POST, and the functionality for working with sessions and headers is baked right in. Languages like Java, Ruby, Python, et al. need special frameworks or libraries to do these things comfortably. Detractors can complain all they want, but another language won’t displace PHP any time soon unless it can integrate as smoothly.

  PHP将蓬勃发展。 尽管存在缺陷，但没有任何主流语言像PHP那样紧密而灵活地远程集成到Web堆栈中。 我们可以使用$_GET和$_POST直接访问传入的数据，并且处理会话和标头的功能也已包含在内。Java，Ruby，Python等语言都可以使用。 需要特殊的框架或库来轻松地完成这些操作。 批评者可以抱怨他们想要的一切，但是另一种语言不会很快取代PHP，除非它可以平滑地集成。

你的想法？ (Your Thoughts?)

But disappearing blue boxes don’t exist and no one really knows what the future holds. I’ve just tried to observe the general trend of things and conservatively estimate where we could end up. Perhaps some predictions have merit; maybe some are laughable. What do you think?

但是消失的蓝框不存在，没有人真正知道未来会怎样。 我只是试着观察事物的总体趋势，并保守地估计最终的结果。 也许有些预测是值得的。 也许有些可笑。 你怎么看？

I’ll leave you with one of my favorite futurology-related quotes:

我将给我留下我最喜欢的与未来学相关的报价之一：

The best way to predict the future is to invent it. – Alan Kay

预测未来的最好方法是发明它。 – 艾伦·凯

Feel free to post your thoughts in the comments section below.

随时在下面的评论部分中发表您的想法。

翻译自: https://www.sitepoint.com/a-php-from-the-future/

php swoole 未来