Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118788 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 39101 invoked from network); 10 Oct 2022 22:20:47 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 10 Oct 2022 22:20:47 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id A306C18050B for ; Mon, 10 Oct 2022 15:20:42 -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_40,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-wm1-f53.google.com (mail-wm1-f53.google.com [209.85.128.53]) (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 ; Mon, 10 Oct 2022 15:20:41 -0700 (PDT) Received: by mail-wm1-f53.google.com with SMTP id c3-20020a1c3503000000b003bd21e3dd7aso9319336wma.1 for ; Mon, 10 Oct 2022 15:20:41 -0700 (PDT) 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=qomP53i88SL6YGBt9EkjGzY6UQETEjrow1K8Z28xeEQ=; b=ZLjI88cWIfts0XStfxJBEQHkj9jwbiZt5RM8FSNTSL2YrE071BFv8Idj8tX3FZQyHB bmzISQvtzJSWCYE5CJddd7mjAMbFq2HCVlryniIqsh8C9E1BNDF3UOVxS6U3BcUAmeyD FGL8Ye+TVkG+KxquRVhRiX1IHKt61DgYgA76Fm/Ly9Ul0qunghTMIco8t8OTnlxQuOzW pBKECgE+BqklDckf/KkpmybVHjFUzRkPt70/y12S4ZT0KWcI4zFyZm8WxbPVSc3/MFAx E3YXf5W39K0F4gOYs7cnxkdXzeECpuVw/T5/uZNt+NLVUtdQ4vjF60W542i3izPPHiAj uglA== 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=qomP53i88SL6YGBt9EkjGzY6UQETEjrow1K8Z28xeEQ=; b=xGxZJoW9mLCW3P6yyFH96wLfyqe3qcMjOH1U7xzqOqM74v+oTR+mtkNGf/AQJE9k26 iKVQLtfWZvhv/xS5jNwHrmioj9Cgvhz6qG1keq+dquXEaWWGjw1SyJ5Cix7Gi/81xKGT xBTjTHIXrltEuP2aT2/bKSUicYYliXDnthgk2fRxYwPvxoVO8ISjXcs1k+hEHrEqa2z4 o9/Kga3OdQKmeYADMBCUgThpp1O3u2wNlBOe+J3BXeYtICQTdftlPpmI979C2nMGPzmE nKYCYPgxFhGm/q3t8n6AKrbBQ5+zQILMVHxwvG5B92T83zxzt1OmNpfe+sJdW2MJl0PP Gg5g== X-Gm-Message-State: ACrzQf1hQB2DZ+f4P3fsIsdy3EgoCCsE1sICisvZNZK+g9luvvs+1Gta XqNOJI455ZsCBcQTnFlaQorsaoF3BW4ZvXHzV0JkX0hDUq8= X-Google-Smtp-Source: AMsMyM68uHDVzkXd6iRLzEf+UlOZoY89cAl/PzEM/JV2UYYHH3yu4p8vD39X/SnGyHbKJDEt0aUA7+SRSHOz1iv6gv8= X-Received: by 2002:a05:600c:4e91:b0:3b4:bcbd:b641 with SMTP id f17-20020a05600c4e9100b003b4bcbdb641mr21711870wmq.59.1665440440535; Mon, 10 Oct 2022 15:20:40 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 10 Oct 2022 23:20:29 +0100 Message-ID: To: David Rodrigues Cc: PHP Internals Content-Type: multipart/alternative; boundary="000000000000da4ce405eab591cf" Subject: Re: [PHP-DEV] Experimental features From: davidgebler@gmail.com (David Gebler) --000000000000da4ce405eab591cf Content-Type: text/plain; charset="UTF-8" My two cents... Why can't "common users" install a PECL extension? It's not a difficult, obscure or undocumented process. I can accept the reasoning > Apply a PECL strategy to try experimental features might not be the convenient way always, for example, if we create a new ... sensitive ini setting that affects the behavior of PHP somehow... OR ... what about a new sensitive funtion in a "core extension" like JSON? But why would the answer in those cases not be "compile the PHP fork/branch with the experimental feature", rather than find a way to flag the engine to switch arbitrary new features on or off, complete with all the complications in the primary source code that would cause? We are, after all, talking about features which by definition should not be relied upon for any production use. Or we're talking about features which are stable and valuable enough to have passed an RFC process, but then what's gained from an experimental designation? Why couldn't they just be included in a preview/beta/RC version which anyone could decide to run or not? --000000000000da4ce405eab591cf--