Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119454 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 62945 invoked from network); 2 Feb 2023 21:00:12 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 2 Feb 2023 21:00:12 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 8D1A11804A9 for ; Thu, 2 Feb 2023 13:00:09 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-vk1-f181.google.com (mail-vk1-f181.google.com [209.85.221.181]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 2 Feb 2023 13:00:08 -0800 (PST) Received: by mail-vk1-f181.google.com with SMTP id b81so1559088vkf.1 for ; Thu, 02 Feb 2023 13:00:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Iw6rq4Is6M1c0JfETMrNLuxXev5BF/X/4safdM+JgLo=; b=IAF0Qqkc/k7GiabujMI/6YYkBWkWLz/5Y2GALunuN1mqsqi57DDwspoJr01aXNA2gK vIvHH40z0ACKBko9gBmIq2kszrTyfSnoQSfcTpadjxQF6YsdFijizmJ0mmz/YxT17hM1 /Iy0/LPUrNNFnFkXlL+UmCjB1GqbqB4vCBYLe/HVg/OHcW2i8hUY6tORw4oohW3BVAPP d22+OEAGW2XxTogwLtiZx9JM6GkSbwLFHS1lCn/Ti3T5hC+hsMDykfYnKeMfPM3BCwzM sA+ekD+F6gVuvU1omcBR/GufWhD6BnDEr9z1B1JNZnuDdSjtIJ1tmubq13IJc/GWOG0r GTyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Iw6rq4Is6M1c0JfETMrNLuxXev5BF/X/4safdM+JgLo=; b=d27C8tI8T+gsprwdOLY95RoYuTnMkcdX0evdiVHilqFtfLQBmoB5h7Lc1zeOBv56t5 GQwEDbhH4DxyNQ/malNqTWaCF6QZG6r1YBi/Orwph2rE/TkKEb//qButMHOP92rvlPbq r5HJI7x5EFroYSzbpTLwUEezpd0WKp8q0NKokOfIE2SbH1RZxgYK0E7fvCZ+VO1fd3bO U2GYlguOZVN0igL7iXaB4EuAPtDpHd61c7iuKGJacNQyNvHAR1bsqGyUFP8eermTHE6t gmjdMUodWV67bC8oY6O/fAK30cuvdXV3795rjSP42hkIICcxlyf2Wgl/vdWBuTYlbRuv kLIA== X-Gm-Message-State: AO0yUKW2+YmrFWS89Oh8u2URtsjoPxAVdJ8Na+ZnrT1ZAwmywJtAconO SEsAwvJ+bgjI8uOwGL5wbNv0GwJYplsaxvlYQR0= X-Google-Smtp-Source: AK7set+5hXjxY9/JlOtIVQ5Lx0UVVmZSDGTb8vNHQrq9lnUizTFYV11nb6KeM6dC4BtaaNBRf3HnuT0GVdmgVw9LPjk= X-Received: by 2002:a1f:fece:0:b0:3e1:78a6:acd3 with SMTP id l197-20020a1ffece000000b003e178a6acd3mr1112793vki.13.1675371607838; Thu, 02 Feb 2023 13:00:07 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 2 Feb 2023 17:59:55 -0300 Message-ID: To: someniatko Cc: php internals Content-Type: multipart/alternative; boundary="0000000000008d575d05f3bdd9ae" Subject: Re: [PHP-DEV] Re: Official Preprocessor From: deleugyn@gmail.com (Deleu) --0000000000008d575d05f3bdd9ae Content-Type: text/plain; charset="UTF-8" On Thu, Feb 2, 2023, 11:22 AM someniatko 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. --0000000000008d575d05f3bdd9ae--