Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118751 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 35862 invoked from network); 5 Oct 2022 12:28:39 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 5 Oct 2022 12:28:39 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 7E1671804BA for ; Wed, 5 Oct 2022 05:28:38 -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,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-yb1-f182.google.com (mail-yb1-f182.google.com [209.85.219.182]) (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 ; Wed, 5 Oct 2022 05:28:37 -0700 (PDT) Received: by mail-yb1-f182.google.com with SMTP id f189so20101543yba.12 for ; Wed, 05 Oct 2022 05:28:37 -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=iYYcV+dYGxxkcxkLpc4+/+QLVsWbLcEWBaunrre8xGo=; b=PFMPIXLasyniaN/7oqHg+THrCwkoh2vj/8myxf7YwGxid9hN9z6xMLgsKA/1ObSTXb rfsl+tJ0mvJZAU30vr5vchsVE4tTorY3/TsFW6Z1SUBXB8GMVzf7GpLe13zuctqy6v6J mwcVQDokoASGntO1tRsOeFG+I/knQva9aLX8r7+gX6kJIAyyLfpzK5wtvLm5T8SA+/ZI WYSH7yN6KuPsu+7W/QxjVt22bAV4LgU7wBKWmvX3a37UJ7sTav+2PXAnQPTie4+4gNVv ap1S0bA50/o+OeAmBfzQVm1VHCehLBKwJ2B45Gi0God7sA8xeE65ozgLfQooj/udR+Jw gd3w== 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=iYYcV+dYGxxkcxkLpc4+/+QLVsWbLcEWBaunrre8xGo=; b=8DeSvB1sJ6Sp9yHaae7eXoufuWzRQt9GLjK+FFsPzN4SlTs3yRxW8uAh53Y9SqfSB/ pa4sz/Q6h/piPhs3b/EtfboHx7kJxaJSZyGl2RTizfIMQoqvK/3/eCIroYbNk7u958Sc z4IW8WE6CXrHF1e5Zx1L9CuVy/DCe7iRsWWWXNSDCy7b35ztcx0fskZ6T6ceVpvvlV0O o0jRIi0GRbEIAsZOT6Qf3yPAdg58up+ODtuMn2yXBXaWozugKVFa5mx9i6dp6jPQCGtf vbA6i5gnyXprZQzwf4DJPkI1tMOI1dJzFo3EzUKrsWK1OezFVT8hSuKi0li4iIjHwhYQ YSsQ== X-Gm-Message-State: ACrzQf2NN8Pi4kFSn7Fz4jWgIu+IshCvaftiWtc0om6U/3/e+H1Nh9bJ 7Z01ZyJhyMfMvOpTPGOm/yoGORmmkE/BDPVteuXSRFKq X-Google-Smtp-Source: AMsMyM6qhVHLRxFlsxxcK/D0eIhII49rFVQco1isZ3WAQbdTl89HOpU7EYE23DzHQdWdGKU+e/JYc2xRdKfTb2GCzpY= X-Received: by 2002:a05:6902:92:b0:6b2:bed3:5eec with SMTP id h18-20020a056902009200b006b2bed35eecmr28222807ybs.60.1664972917322; Wed, 05 Oct 2022 05:28:37 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 5 Oct 2022 09:28:26 -0300 Message-ID: To: Deleu Cc: juan carlos morales , David Rodrigues , PHP Internals Content-Type: multipart/alternative; boundary="0000000000004c368305ea48b759" Subject: Re: [PHP-DEV] Experimental features From: flaviohbatista@gmail.com (=?UTF-8?Q?Fl=C3=A1vio_Heleno?=) --0000000000004c368305ea48b759 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Oct 5, 2022 at 8:16 AM Deleu wrote: > On Wed, Oct 5, 2022, 7:54 AM juan carlos morales < > dev.juan.morales@gmail.com> > wrote: > > > > > 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, then ... > > maybe applying the PECL strategy might not be the most confortable way > > to approach it, OR ... what about a new sensitive funtion in a "core > > extension" like JSON? > > > > Just to build up on this. I feel like Extensions are maybe a technical / > development feature that may have the power to address the issue, but fro= m > a "Product" (PHP language as the product) this isn't the best. Anything > behind extensions add a significant entry burden and reduce the reach for > users of the product, be it for lack of trust, knowledge or lack of > infrastructure that allows such changes. > > > > Deleu & Juan, Thanks for clearing this up! A product approach could be something interesting to explore. I'm more than happy to join and help anyway I can. --=20 Atenciosamente, Fl=C3=A1vio Heleno --0000000000004c368305ea48b759--