Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118749
MIME-Version: 1.0
References: <CAEsg9X3LGYQiF6PGgfhY9s=4iD5v0u2scFRyekNtJfcKDMijtQ@mail.gmail.com>
 <CAAwFBqoG0wjRxVXC8FvBHv5uCJYVYNJWLEGTnAX7DiYUO3rpVQ@mail.gmail.com> <CAEsg9X0YmHEqcoE27rGK2ixndSHFNAeCJcSC4JGvdFu6daz-cg@mail.gmail.com>
In-Reply-To: <CAEsg9X0YmHEqcoE27rGK2ixndSHFNAeCJcSC4JGvdFu6daz-cg@mail.gmail.com>
Date: Wed, 5 Oct 2022 07:54:11 -0300
Message-ID: <CANMwmbPLgxjDrmsDDVLEZJ+s3StrzDrSct-hL1wE-5O+Kh4NhQ@mail.gmail.com>
To: David Rodrigues <david.proweb@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Experimental features
From: dev.juan.morales@gmail.com (juan carlos morales)

My small contribution to this ....

First of all, nice you picked "json_validate()" for your example,
thanks for this, somehow, support! :)

Second...

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?

An Experimental feature is something that WE want it to be in such a
way because we want to see how the feature behaves, and what can of
feedback can we get out of it.

In case this proposal is accepted, it will change the RFC process for
sure in order to indicate if its experimental or not.

I think Experimental features , no matther what they are, should be
backup with a consistent monitoring strategy around them.... something
to keep in mind; This proposal is more about workflows in the PHP
project than something else.