没必要。。。那点性能和 codeignitor 差不了多少，因为都是 fpm 机制
真追求性能上 swoft，然后这个大部分人 hold 不住

对自己宽容一点，别太在意别人的看法

The Future of the Zend Engine and the Zend Framework
In the past 20 years, I've been at the forefront of the development of the Zend Engine - the 'kernel' of PHP - both personally and via my team. We led many of the key advancements in the language runtime, including most recently the development of the updated brain that made the wonder that is PHP 7 - and many other things over the years. We're very proud of these contributions, and I believe they had a critical impact in both the rapid proliferation of PHP in the past - and for keeping it competitive in recent years. Other folks in my team have led the development of other prominent components in the PHP ecosystem - namely Zend Framework, Apigility and Zend Expressive - which too are being used by hundreds of thousands of companies.

In the last three years - after Zend was acquired - we continued to do this work under the umbrella of Rogue Wave software, for which I'm very thankful. However, Rogue Wave has recently taken a strategic decision to focus its efforts on the Zend Server part of the Zend portfolio. Consequently, I'm announcing that my team and I - including Dmitry Stogov, Matthew Weier O'Phinney and Enrico Zimuel will be leaving the company and looking for new opportunities. This isn't going to happen immediately, but the decision has been taken.

As all of us still care very much both about PHP as well as the Zend Framework ecosystem, one of the options we're evaluating is finding a new home for these contributions, to keep both our planned contributions to PHP 8 and beyond on track, and the ongoing development of ZF and Zend Expressive thriving. One of the reasons for this announcement - which is coming well ahead of our actual departure date - is to explore this possibility.

If you work for a company that you believe be interested in supporting such an effort, I'd love to hear from you at [email protected].

vendor 目录下的东西不能手动改的
要加载自己的类在 composer.json 里面弄好 psr-4 加载路径

@43QYK2JU 你这么睡的时候怎么处理光线问题和防虫问题呢，类似《摇曳露营》那样打个帐篷啥的？

看到了的确如： https://github.com/Yurunsoft/Guzzle-Swoole/blob/0b86b1e1448ad0ec1f30ad6dfd545ed037dd4295/src/Plugin/Plugin.php#L107

等等，这个机制会去修改 vendor 下的源码？这么做太脏了吧

支持，和 saber 比看鹿死谁手

google 之类的厂不允许员工睡公司是因为怕背上压榨员工加班放弃私生活的锅吧，我记得有 google 的哥们直接把房车开过去直接房车睡的

这个解决方案不错，这楼里很多人就是被保守迂腐的观念框住了的人，一旦有人采取一些新的不同的解决方案，他们就会不舒服觉得你这样不对那样不对，don't care

顺便，米家的人体移动感应怎么和空调联动的呢？

@lucyatwex 没啥问题。。。话说推荐上 tidb 吧，更省心。。。hive 啥都有些查询出了错你不知道咋回事，tidb 出了问题找 pingcap

@ylsc633 对 php 底层有一点了解或者对后端积累比较多的都可以说出这个复杂度，我反而认为这是很好的甄选方法

@sunmonster 其实 async/await 以及 promise/yield 并不是一个好的解决阻塞的方案，和回调一样有 callback hell 问题，因为会有调用栈传染，最后搞得很复杂。。。你说的这个 rfc 里面可以找到： https://wiki.php.net/rfc/fiber，但是这个很鸡肋，zanphp/php-msf 等框架就是代表，很难很复杂。。。现在 swoole 有像 golang 那样的全协程了，php 在这里发是领先的： https://github.com/swoole/swoole-src/blob/master/examples/coroutine/coro_nested.php

变量强类型估计不会做，因为做了这个 php 就不再是脚本语言了，韩天峰在尝试搞强类型的 php 也就是 typephp，老实说我比较怀疑这个的应用场景

@sagaxu 恕我直言，这是不太可能的。。。因为 php 照顾的肯定是 fpm 生态，而 fpm 生态里面 gc 已经够用了，而 jit 很难提高太多性能了，至于泛型那更是不需要的，多线程本来就有

鸟哥的团队吧，CV 这行不好混

楼里某些人要 block 就直接 block 就好了，你都 block 了我了还跑来回复我然后 at 我，这是啥心态？

没有这些破解的人你手机 root 都玩不了，某些人就知道人云亦云，不用大脑思考，连最基本的平衡都不懂