2 min read

Yesterday, Symfony, a community of 600,000 developers from more than 120 countries, announced that it will no longer be a member of the PHP-FIG, a framework interoperability group. Prior to Symfony, the other major members to leave this group include, Laravel, Propel, Guzzle, and Doctrine.

The main goal of the PHP-FIG group is to work together and maintain interoperability, discuss commonalities between projects and work together to make them better.

Why Symfony is leaving PHP-FIG

PHP-FIG has been working on various PSRs (PHP Standard Recommendations). Kévin Dunglas, a core team member at Symfony, said, “It looks like it’s not the goal anymore, ’cause most (but not all) new PSRs are things no major frameworks ask for, and that they can’t implement without breaking their whole ecosystem.”

The fact that the major contributors left the group could possibly be a major reason for Symfony to quit. But it seems many are disappointed by this move of Symfony as they aren’t much satisfied by the reason given.

The matter of concern for Symfony was that the major projects were not getting implemented as a combined effort.

Something similar happened while working towards PSR 7, where no commonalities between the projects were given importance. Instead, it was considered as a new separate framework.

People are still arguing over why Symfony quit.

Will the PSRs die?

With the latest move by Symfony, there are various questions raised towards the next step the company might take. Will the company still support PSRs or is it the end for the PSRs?

Kévin Dunglas has answered to this question in one of his tweets, where he said, “Regarding PSRs, I think we’ll implement them if relevant (such as PSR-11) but not the ones not in the spirit of a broad interop (as PSR-7/14).”

To know more about this news, check out Fabien Potencier’s Twitter thread

Read Next

Perform CRUD operations on MongoDB with PHP

Introduction to Functional Programming in PHP

Building a Web Application with PHP and MariaDB – Introduction to caching