Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75820
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
Message-ID: <53CE0CB0.4080703@lsces.co.uk>
Date: Tue, 22 Jul 2014 08:03:12 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <b39ebab3d19d76cda9bafa25919c0e67@mail.gmail.com>	<CAGa2bXahqscNFe5Dy7Lc6NcjZDfw+tkNBtM8Z8p-+n7anq8gew@mail.gmail.com>	<df087915cfde8c749fd9551953a3ca40@mail.gmail.com>	<CAH-PCH7jd6D=sP6MaAD4tK-F0SRXpWj3_bzie9y5ZqeL-Gi3cA@mail.gmail.com>	<aa6e605aa20062ea943b550d342ae222@mail.gmail.com>	<CAH-PCH7jHQK4w3cqqf3S+HrxbjY_jHNCUJY5OpB6oH7VNQJn=A@mail.gmail.com>	<-6299216022086038902@unknownmsgid>	<CAH-PCH4pxuWDk7sFudHix_OeVVfusUYZ6i89kKCOaGSSJNFBeA@mail.gmail.com>	<CABBJUpe1DwZL30J3w1csmuFzGZJ01gQakHMSN7MtdCN+xLXekA@mail.gmail.com> <CAEZPtU7AsGvioOEebZa0o+peZZtsEVp5NAVnFnU+m-H+iWzTVg@mail.gmail.com>
In-Reply-To: <CAEZPtU7AsGvioOEebZa0o+peZZtsEVp5NAVnFnU+m-H+iWzTVg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: Move phpng to master
From: lester@lsces.co.uk (Lester Caine)

On 22/07/14 03:58, Pierre Joye wrote:
> Now, as I already suggested many times (but with zero reply from
> Zend's), let step back, get our roadmap setup, todos, goals, agreement
> and get back to work. But a forcing move to php-next within a year
> with almost only phpng is a major mistake and will most likely create
> a major problem within the php community, especially for php.net. We
> are not in a positiion to do such mistake,. It is time to get our
> stuff together, to work as a team, this is out last chance, and phpng
> is not worth it in comparison.

Perhaps it may surprise some people, but I totally agree with Pierre
here. Given that the majority of MY time is spent these days trying to
play catchup, I am only really interested in fixing the remaining holes
in the user end of PHP. Rebuilding the guts really has little interest
... I've been through the same exercise with Firebird and we still use
the older versions because it does the job! Much of the esoteric
additions to PHP have absolutely no interest to me and in many cases
it's these which are creating the problems phpng is now trying to fix?

When I started at this lark 10+ years ago I could write PHP5 code that
gracefully rolled back to PHP4 and just worked. These days I'm not even
sure exactly what I'm even trying to fix ... I just work through a list
of warnings ... that is AFTER I get rid of the white screens! NOT having
control over much of the shared hosting environment I'm having to work
with, the current spread of incompatible configurations is a major
roadblock, and what is stopping even PHP5.2 from being phased out :(

Perhaps it IS time to reinstate PHP6! We know what the mistakes were and
have a better understanding of how things should have been done. With
the rest of the world already using Unicode and 64bit hardware, it's
these areas that need putting to bed in the core which is much more
important than a major code rework. Then phpng can be PHP7. Trying to
continue to shoehorn improvements into PHP5.x without the flexibility to
break the bits that DO need breaking is what is holding up progress, and
if phpng has been developed properly then it can be merged in again
later ...

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk