Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109214 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 77429 invoked from network); 23 Mar 2020 00:44:39 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 23 Mar 2020 00:44:39 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id CB4361801FD for ; Sun, 22 Mar 2020 16:08:41 -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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS 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-f43.google.com (mail-wr1-f43.google.com [209.85.221.43]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sun, 22 Mar 2020 16:08:41 -0700 (PDT) Received: by mail-wr1-f43.google.com with SMTP id f3so14728197wrw.7 for ; Sun, 22 Mar 2020 16:08:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=3zPdw+b3qAS0WB+csHt9vT5gat8RnEPfZD6fK10rJtg=; b=k46c84fZVyZxz9DUX/p26xOE3BOvHjK94K5OiOUVrx8CW1xeitqtntlkkZGr2bYJwo qQbd3TaX1Tf98AJK4clkG5j2KewbsaJZKdMgnCRx0GQi2F6DGrpKNj8XyFzMCyI14Mne ccsyVa1W3ggEixRkZgHK+sKi70qohEcorYpfrOfIAmDk27wdb/6Q4jrE0FKKVLmJBQHN mvUwKyyFjbB5lRa/MS41Uui8b9hWtz6/7xoh6Y+Zk+m513rQysTzCfJE9K6yYCPG8ml4 NMFieeAam7xzKDw6WCVsca3SaB3mLWfO1GOjGKwsqbt32UBylPcczxl1SgCmq0QQrnIh VAtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=3zPdw+b3qAS0WB+csHt9vT5gat8RnEPfZD6fK10rJtg=; b=rhvBkk+ttle4rrbPDa5Sw+rWy2Nur3qsrzogkpquNfN7k9ooOECcVLvCNzrTGfsv5m 8cf576i7Hl78YS+dDIJShxHSRqXldPtOFZZKlWtTDCjFQFA9hwv0D5qGfpI844/gR1II 17i+9sJ6RensTIOYgQJ5b/jPt085lOQYw07JUrARuv6cOrUFONQhnLcej3HC6qaWXMNQ sg0rjvCR/27FhUOD04BV5GwsoBC4lT0FJag5t33A7EjSlXsAW2CGuA+iCt5lzP6cdxoQ 31Ni4jrL6ll/IdUNs6OezoW8j3es/4QhhoNl9XlOG/DesrqXBaGXXzrPpj4uTviBJc6F XUrA== X-Gm-Message-State: ANhLgQ3Lp5PRPUm1n/tQxZv1MpFNRSlQElDSvU/qK+m08RTdYFOV8BW1 D6SHEt8c8uS9msum10iIXy+9lrev X-Google-Smtp-Source: ADFU+vsxfoZD/mYJnzErqo3Vt1a0U2X6iymriOsh5fFDfCFuCQzx2creEu6glhkX0Q+diphJT1zmBA== X-Received: by 2002:a5d:484d:: with SMTP id n13mr13885229wrs.387.1584918519025; Sun, 22 Mar 2020 16:08:39 -0700 (PDT) Received: from [192.168.0.14] (cpc84253-brig22-2-0-cust114.3-3.cable.virginm.net. [81.108.141.115]) by smtp.googlemail.com with ESMTPSA id c85sm19452401wmd.48.2020.03.22.16.08.37 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 22 Mar 2020 16:08:38 -0700 (PDT) To: internals@lists.php.net References: Message-ID: <01dc25c6-0dd5-42a6-bbf5-00656baefbd3@gmail.com> Date: Sun, 22 Mar 2020 23:08:37 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB Subject: Re: [PHP-DEV] Are PECL modules preferable? From: rowan.collins@gmail.com (Rowan Tommins) On 21/03/2020 22:52, Mike Schinkel wrote: >> On Mar 21, 2020, at 5:59 PM, tyson andre wrote: >> FROM: Re: [PHP-DEV] [RFC] is_literal() >> >> And if it can be implemented as a PECL module, that would be more preferable to me than a core module of php. >> If it was in core, having to support that feature may limit optimizations or implementation changes that could be done in the future. > Just wanted to address this comment which was made on another thread (I did not want to hijack that thread.) > > A large number of PHP users have no control over the platform they run on, so the option to use PECL modules is a non-starter for them. Even if a module is "bundled", that doesn't mean it automatically becomes available to all vanilla builds of PHP. I know that a lot of Linux distributions break up their PHP packages so that pretty much every module can be installed separately; conversely, they provide pre-compiled packages for a lot of PECL and third-party extensions. So there's very little difference between installing, for example, "php-zip" (bundled) and "php-redis" (PECL). I glanced at a couple of the WordPress hosts you mentioned, and couldn't find a clear description of their PHP configurations, but I suspect it's similar - some "bundled" extensions won't be enabled (e.g. various database drivers), and some PECL extensions will be installed as standard (e.g. Redis). In practice, I think there are four types of extension, not two: A) Core, and either can't be disabled, or disabling is very rare B) Bundled, but optional; may be packaged separately; may be optional or not supported by managed hosting C) Not bundled, but widely available pre-built as well as through PECL; may be included or available in managed hosting D) Not bundled, and not widely pre-built; mostly available only via PECL Type B and C enjoy similar availability to users, but type C allows a package maintainer more freedom to maintain and evolve the extension; type B trades that for a rubber-stamp of official approval. Regards, -- Rowan Tommins (né Collins) [IMSoP]