Hello ! Le dimanche 15 mars 2026 à 13:44, Daniil Gentili <[email protected]> a écrit :
> In other words, feature extensions are "guests" allowed into the > php-community branch, or PIE extensions "pre-installed" into PHP, and are > developed and maintained exclusively by their owners just as if they were a > standalone extension, with some overview from `php-src` maintainers, yet > maintaining independence on design/API choices (again, as if they were > standalone extensions). I'm following this thread and it make me think about the current extension landscape. Maybe I'm a bit naive here but I think that this discussion can give more room to extension development: * Extensions are outside of the php-src and maintained by their maintainers * Extensions can interact with PHP core without adding work for the current maintainers * No need to distribute specific PHP versions with available features. Also I'm afraid that if we have a lot of different features in the progress that will create a crazy possible combination matrix. How to ensure everything behave correctly with all the others, or only some of them inside the community version? So I don't understand why we need the php-community version if it contains "only preinstalled" extensions that users can experiment themselves. Maybe it can allow verifying adoption but that means users that will switch to the community version for a daily usage and it'll split the user base. However I think deeper features and experiments are important. I think that extension can't completely change PHP behavior today, extensions might only have access to specific part of the engine lifecycle. Maybe it can be interesting to add more hooks so extensions can leverage deeper features and changes? I think it can simplify this RFC by having a complete separation between the engine, stable and production ready and the experiments (which can stay extensions). With PIE it's now easier to install extensions and also test them. This way users can install extensions, tests features. An extension become really useful it can still be merged in the core like it was done in the past (maintainers can still maintain the core part). Thanks Stéphane --- Stéphane Hulard https://chstudio.fr
publickey - [email protected] - 0x01B6678A.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
