Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118431 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 15693 invoked from network); 14 Aug 2022 18:02:42 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 14 Aug 2022 18:02:42 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0C9A21804BE for ; Sun, 14 Aug 2022 13:05:33 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,NICE_REPLY_A, 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-wr1-f48.google.com (mail-wr1-f48.google.com [209.85.221.48]) (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 ; Sun, 14 Aug 2022 13:05:32 -0700 (PDT) Received: by mail-wr1-f48.google.com with SMTP id v3so6992946wrp.0 for ; Sun, 14 Aug 2022 13:05:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=0W1jIDF/BsnXFENKN477nji2uJbghBfW8SonUAFa4uE=; b=RjbxRa7S50ZTMs4/mci5jPgC+PGnb8VRQZ2/CAflsTAxkEl5QCtsRLVp+dN/gZmDvR 7NrZA7VniozGNKQR7BVsM9F1lQlccWwrSI7ViwLdZxmUmrQ9Y0G0ijwRK3hsl5ycjzra /I5lGC6MjdkGmMxekU4hd0oC3ZJWAA9AWV77J830Stmw/JnjbiJqb0/7DYEqhjtn6SOl Yi3pWSu7je9tFNyVgzhbc6xqjNjknRUx2TQEuXBMeFmlFhnSZXOF9e7gHleCMmSldaJa /IgNUHpZmuD+DPss4v/pWrLlHqPqj9nmLqfadGOgDW/MT9oK63uzAHodogHyj+FyKXfu MMRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=0W1jIDF/BsnXFENKN477nji2uJbghBfW8SonUAFa4uE=; b=vHczMWBBnpw1IeS0QT14BL5G5HlpWSGCAWIQavQ/6aCaB8RdxNmHn8rVeZGan+ZW9a 9147r38i9jpQSOSHLlWNiEURsqF6oMfC2XUpjHAF0XCtyMvmPLM568m4b5mH2Trjn6FV 1xclqB7L0Tzt2xegyVXMMtrvqpIw1XMIjvgNMhrCKGbuTclCypor0xpnVACK4y03L56j GO47IsWTneA7dgEvT8k+Ni5BQ7RjEanOCqcF1hkFlSPWO2SleBAk4qPUVgxtQSNf1vjN t950nSOngaF4LYUGUG63vM0eyhSx4JTYpnXfKhSZYo08jDlLM+fn35zS/n0TN23LaxSG ANJQ== X-Gm-Message-State: ACgBeo2Q8zdrFA1ZBEcfW/zJ6G7ecHfZZ8ZFWZqx+vU42siFjLozsWYH h0kgQtkeuMnk3U7o5+HMoXaeQtdPCQs= X-Google-Smtp-Source: AA6agR5ZdcxXKx4h5EHmkgZLVB8xHigGklVMhlN6LHEzvApj1V4EGHFKa/nuCqHo5gkHM0a9x4d8Iw== X-Received: by 2002:a5d:60c5:0:b0:220:6780:2701 with SMTP id x5-20020a5d60c5000000b0022067802701mr7269733wrt.450.1660507531278; Sun, 14 Aug 2022 13:05:31 -0700 (PDT) Received: from [192.168.0.22] (cpc104104-brig22-2-0-cust548.3-3.cable.virginm.net. [82.10.58.37]) by smtp.googlemail.com with ESMTPSA id y2-20020adfe6c2000000b002207cec45cesm6752155wrm.81.2022.08.14.13.05.30 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 14 Aug 2022 13:05:30 -0700 (PDT) Message-ID: Date: Sun, 14 Aug 2022 21:05:30 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 Content-Language: en-GB To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Executing PHP SAPI/runtime from Golang/Rust From: rowan.collins@gmail.com (Rowan Tommins) On 14/08/2022 13:29, Paul Dragoonis wrote: > Moreover if you're looking at reasons people have previously or currently > moving away from PHP to other languages, due to limitations like pure async > or concurrency stuff .. then perhaps a new FRONTEND which can execute the > PHP runtime on the backend would be solving some things. There already are concurrent and asynchronous solutions for PHP: Swoole, Amp, React, etc I think part of the reason they aren't more popular is simply that they're young compared to the language itself - one of PHP's big advantages is its thriving ecosystem of existing software, frameworks, and libraries. A lot of those need modifying to take advantage of a concurrent / asynchronous environment, or even to run safely at all, because they assume PHP's traditional "shared nothing" model. By contrast, the ecosystems of node.js, Go, etc have been written with concurrent / asynchronous already "baked in", so are fully ready to take advantage of it. If you need to rewrite large chunks of your codebase to use an async-friendly framework anyway, it's less of a leap to switch language completely. Regards, -- Rowan Tommins [IMSoP]