On Thu, Feb 2, 2023, 11:22 AM someniatko <somenia...@gmail.com> wrote:
> I'd like to also emphasize that the concept of compilation and static > type-checking / analysis is not foreign to the PHP community. Major > frameworks like Symfony already have a concept of compiling e.g. a DI > container, and static analyzers like Psalm, PHPStan and others are > actively used. > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php I think the idea overall is pretty solid and could get a few community supporters. But the devil is in the details. 1. Making it official is a trade-off. It's the highest chance of widespread adoption and the heaviest burden on PHP Internals. 2. Who's going to fund it, develop it, maintain it? It's a significant project and a heavy burden. 3. What's the MVP? How do we measure usefulness, adoption and maintenance complexity? 4. Is it an aborttable idea? If things go south and can't be supported anymore, how bad for PHP adopters would it be? 5. How would voting on the spec be like? Complete years-work-hours spec or small incremental functionalities? 6. Is versioning tightly coupled with PHP version or does it have its own version support system targeting multiple php versions at the same time? Overall, I think PHP has been constantly losing popularity in favor of Typescript and a transpiler could create an exciting solution for some of PHP's problems, but it does not seem like a pet project.
