Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75300
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53BA8E93.8060708@lsces.co.uk>
References: <61EEC54E-7B8D-433E-A391-75F8D6A41E79@ajf.me>
	<650742796f119ed972a688a58e02242b@mail.gmail.com>
	<CAEZPtU7WuRQToC6MVoqz7-O2TFL3Q6vgp4ZUD6dto0pkn-4bFw@mail.gmail.com>
	<53BA8E93.8060708@lsces.co.uk>
Date: Mon, 7 Jul 2014 14:19:27 +0200
Message-ID: <CAEZPtU4TPqZ5mt8r8BjC-kWq9-V79pFNRHLCWPzZXCp02QYPmw@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Name of Next Release of PHP
From: pierre.php@gmail.com (Pierre Joye)

On Mon, Jul 7, 2014 at 2:12 PM, Lester Caine <lester@lsces.co.uk> wrote:
> On 07/07/14 12:31, Pierre Joye wrote:
>> I seriously hope that you take 2015 as pure example here. As I see no
>> remote chance to be ready next year. PHPNG is a huge stack of
>> undocumented perf patches far from being ready, APIs &code cleanup did
>> not even begin, and the existing APIs are even more ugly. This is not
>> going to be a small task, besides other things that we may like to
>> have in the next major version. A 2 years development period sounds
>> much more realistic to me.
>
> If that is a realistic roadmap, then what also needs to be added is just
> what happens with the PHP5 in the meantime. From my own view, some
> elements of 'PHP6' are still overdue, but if it will be yet another
> couple of years then should we be looking at an interim solution for
> 'bigint' and unicode? While reworking the entire code base to give a
> performance improvement is a perfectly sensible long term plan it
> sidesteps the 'problems' that PHPNext should ideally address. There are
> perhaps two conflicting paths here?

I am skeptical on bigint in the engine given what is possible now in
gmp. But yes, phpng is also a problem as it creates a total new code
base and barely blocks any other improvements. Why? Except that bigint
thing, I do not see many people trying to add stuff based on phpng at
this point, it is a moving target and will move a lot in the next
months as well. But this is a topic for another thread, this one being
about the version number and this exact RFC.


Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org