Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74301
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <A5BF8ADD-121B-487B-8FA3-DCAAA254362E@ajf.me>
References: <A3E9D7E0-5C10-48AD-B141-F3D72B74A235@ajf.me>
	<4818449979808f1f4d0fcdc1409d9e04@mail.gmail.com>
	<A5BF8ADD-121B-487B-8FA3-DCAAA254362E@ajf.me>
Date: Sat, 17 May 2014 22:25:00 +0200
Message-ID: <CAEZPtU71bFYbd9BvXUJ7w4OJmKax2Jy-shvejShzKXFYbD6zdw@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Zeev Suraski <zeev@zend.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Proposal to increase the required majority for all RFCs
From: pierre.php@gmail.com (Pierre Joye)

On Sat, May 17, 2014 at 9:50 PM, Andrea Faulds <ajf@ajf.me> wrote:
>
> On 17 May 2014, at 20:46, Zeev Suraski <zeev@zend.com> wrote:
>
>> Implementation changes don't fit in this RFC process too well.
>> Implementation changes should be dealt with by those who own the
>> implementation.
>
> I don=E2=80=99t and can=E2=80=99t agree with this. Zend changes will ulti=
mately affect everyone.
>
> It is not just Zend maintainers who=E2=80=99ll be affected by the 64-bit =
patch, for example. Everyone would, as it would increase PHP=E2=80=99s memo=
ry usage.
>
> Also, I am unconvinced that just because the people who maintain Zend (sa=
y) want something, that they are necessarily right.

Cannot agree more here. php4 to php5 and the later versions have
clearly show Zend blocking features that have beeb implemented later,
loosing years in the process. RFCs provide a way to reach consensus
and keep in touch with the reality of the PHP needs today and
tomorrow.


--=20
Pierre

@pierrejoye | http://www.libgd.org