Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75824
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.169 as permitted sender)
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>
 <CA+9eiLu+UD91AMoThBOqBHyeZqbwBvFbQm8F+UrP8uBkw9sJJQ@mail.gmail.com> <53CE0EAE.8060602@lsces.co.uk>
In-Reply-To: <53CE0EAE.8060602@lsces.co.uk>
MIME-Version: 1.0
Thread-Index: AQI8QOdx/Do9KUTbDGI5HWlFNEg77gIYs0dnAet77wUBEsDZDAJ6ohvGAqhZZxMBr0peYwJxgNAqAo3QBEgC9OjdRAK2dULEAWRR8uiaErzL0A==
Date: Tue, 22 Jul 2014 10:52:07 +0300
Message-ID: <0587d9fc9ab9ac41fcbfdb499c4e6ab8@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: Move phpng to master
From: zeev@zend.com (Zeev Suraski)

> -----Original Message-----
> From: Lester Caine [mailto:lester@lsces.co.uk]
> Sent: Tuesday, July 22, 2014 10:12 AM
> To: PHP internals
> Subject: Re: [PHP-DEV] RFC: Move phpng to master
>
> Big users don't use PHP ...

Just to elaborate (slightly) on Dmitry's answer  - this is an absolutely
wrong and also fairly dangerous misconception.  PHP is the most widely used
dynamic language out there for web sites, and it's used by many of the
largest companies out there.  In fact, there are very few companies that
don't use PHP at all - whether it's for their main website or internal apps.

Judging by the response to my benchmarks post (10K views in the first 5
days, which I have to admit is very uncommon), the number of retweets,
questions and discussions it sparked - I'd say the level of interest is
very, very high.

I do recommend that instead of wasting time arguing about theory, at least
at this point, we focus on doing.  The first logical step (in my humble
opinion) is to move phpng into master and close any remaining gaps as
quickly as possible.
In parallel, people who want to get additional things into 6/7 should
hustle, instead of assuming they have 2-3 years of lingering to rely on.
RFCs we already agreed are going to be in the next version - like the
uniform variable syntax and the 64-bit patch - will make it into master
pretty quickly, I think we can count on Nikita here.

For 6/7, we should primarily focus on things that we can only do in a major
version - i.e. things that break compatibility.  We should do so while
keeping in mind that this is *not* an opportunity for wholesale breakage, as
then we risk very slow or no migration (like we had between 4 and 5).  New
features can be added in the yearly .1/.2 releases too - so if they make it
into .0 - great, but if not, no big deal.  I stand by my statement that I'm
sure a great deal of users (my guesstimate - the majority) would happily
upgrade to PHP.NEXT even if the huge performance gains were the only thing
there.

Zeev