Urgent PHP #2: Generics Rejected, PHP internals, TypePHP, Nicolas Grekas’ New RFC & Reddit

The hosts discuss the current state of PHP development, emphasizing issues with governance and community involvement. They highlight how the language's decision-making process is hindered by a lack of transparency and central leadership, leading to slow progress on features like generics. The conversation touches on how successful projects like Laravel owe their success to strong leadership and clear vision, contrasting with PHP's dispersed governance model. They advocate for a more centralized leadership approach to drive language evolution, similar to what has worked in frameworks, to ensure PHP remains relevant and modern.

The discussion covers the ongoing debate around implementing generics in PHP, focusing on the rejected RFC for runtime checked generics ('typed checked at runtime'). The hosts analyze the different approaches—type of generics vs. rectified generics—and express concern over the lack of consensus, which jeopardizes the feature's inclusion. They highlight that the process is hampered by diverse opinions within the governing committee and question whether PHP will ever reach a consensus on this fundamental feature, despite increased community interest.

TypePHP, originally developed by the Swole team in China, aims to create a compile-to-binary version of PHP that incorporates static analysis, improving performance and developer experience. Renaming their compiler to TypePHP after the RFC rejection was seen as a strategic marketing move. The hosts discuss the potential of TypePHP to revolutionize PHP, akin to TypeScript's impact on JavaScript, but note barriers such as language, cultural differences, and community integration that could hinder widespread adoption. They emphasize the importance of compatibility with existing PHP ecosystems right from the start for success.

The hosts review Nicolas Grekas' recent RFC proposing a new magic 'exists' method to distinguish between unset and null properties in classes. The RFC aims to address issues faced by data mappers and ORMs needing precise property existence checks. The community's response was largely negative, citing complexity and limited benefits for end-users, as the feature would primarily benefit library authors. The discussion highlights the challenges of adding new magic methods and the importance of clear long-term vision in PHP's development.

The hosts conclude with reflections on how community discussions, criticism, and content creation are helping to shake up PHP's internal development process. They stress the importance of transparency, leadership, and clear vision for PHP's future. They compare PHP’s situation to other successful projects like Laravel, which thrives under strong leadership, and express hope that disruptive projects like TypePHP might motivate the PHP core to adopt more modern governance practices. The episode closes with appreciation for community engagement and a call for continued open dialogue.