请教各位，Laravel 是否退出 PHP-fig？

感觉导火索是PSR6

是的，这篇文章大概总结了事情的缘由，还有后来的发展 http://overnightcoding.com/2016/05/12/php-...

我把主要的贴出来，下面是四个项目，还有他们退出的原因：

[Doctrine]

We have discussed this for a very long time now internally and decided that Doctrine wants to drop out of the FIG. There are several reasons for this, one primarily is the lack of time we have to take part in the discussions and our lack of participation therefore in all of the standards that came after PSR-0 and also that we did not feel any of the PSRs after PSR-4 is worth implementing and standardizing on from our POV.

This is not to talk down the work that has been done here by participants isn’t valuable, we just feel our desire for standardization is mostly reached and everything on top is better solved by competition for the best solutions.

@Guilherme Blanco – May 11th
https://groups.google.com/forum/#!topic/ph...

[Guzzle]

Jeremy, Michael, and I have discussed this for a while, and we feel that Guzzle no longer benefits from membership in the FIG. The existing PSRs have standardized what we need for interoperability, and Guzzle isn’t a framework.

We will continue to participate in discussions as time and interest permit, but we will do so as PHP citizens rather than as project representatives.
@jreskew – May 11th
https://groups.google.com/forum/#!topic/ph...

[Propel]

We decided to leave PHP-FIG due to various reasons, mainly because we don’t have the time to participate in all those PSRs and debates. Personally, I’m also against some new stuff/PSRs that came up in the last months, so I actually can’t support nor justify PHP FIG anymore.

@Marc J. Schmidt – May 11th
https://groups.google.com/forum/#!topic/ph...

[Laravel]

With a few of the other recent resignations (particularly Doctrine’s), Laravel will bow out as well. I must admit I very rarely ever read the e-mails and simply don’t have time to participate in any meaningful way.

@Taylor Otwell – May 11th
https://groups.google.com/forum/#!topic/ph...

大家说的主要原因两个 1. 讨论信息太多，因为忙，很少参与；2. 有一些 PSR 标准不同意。

Taylor 说的是因为其他组织退出，尤其是 Doctrine 的退出，Laravel 也要退出。他因为忙很少查看讨论的细节，所以没有留在 Laravel 的必要。

估计大家还是对后面的 PSR 异议比较大，不过也没有明说，具体为什么只有他们自己清楚咯。

文中提到的一个项目挺有意思的，可以关注下 https://github.com/php-cds/php-cds

@leo 个人感觉缓存接口规范比较啰嗦，不太直观。

PSR 已经做的非常棒了，现行的 6 个标准，已经深深的影响了 PHP 社区。

具体请见：

《PHP PSR 标准规范》

Laravel 目前沿用 PSR2 编码规范，和 PSR4 自动加载规范，短时间内应该不会有太大改变。

https://learnku.com/docs/laravel/master/contributi...

@MrJing 有点管太多的感觉

Doctrine 也退出了。。。

@MrJing PSR-16这个还可以，但还是草稿状态

PSR规范让它太过规范了，这样给框架的自由空间就小了。:joy:

PSR挺好的

一个退出，大家就都退出了。。。