Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66341
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.213.169 cause and error)
Message-ID: <512FA5D5.8060908@lerdorf.com>
Date: Thu, 28 Feb 2013 10:45:41 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3
MIME-Version: 1.0
To: Nikita Popov <nikita.ppv@gmail.com>
CC: Zeev Suraski <zeev@zend.com>, 
 PHP Developers Mailing List <internals@lists.php.net>
References: <435a322ccb14090d3bcf6bf8a110396d@mail.gmail.com> <CAF+90c-FeWE960EJsvpdNu+CpCOyK84=mTyfH_vgUzPRSmD7gA@mail.gmail.com> <3206872690693024300@unknownmsgid> <CAF+90c-x5jNDofLgUgHLnBFRd8Y+qO0yvmPKKdqe3y51cGV0-A@mail.gmail.com>
In-Reply-To: <CAF+90c-x5jNDofLgUgHLnBFRd8Y+qO0yvmPKKdqe3y51cGV0-A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP distribution
From: rasmus@lerdorf.com (Rasmus Lerdorf)

On 02/28/2013 10:37 AM, Nikita Popov wrote:
> On Thu, Feb 28, 2013 at 6:35 PM, Zeev Suraski <zeev@zend.com> wrote:
> 
>> No syntax changes, so regular majority as far as I can tell.
>>
>> Sent from my mobile
>>
> 
> It's not a syntax change, but it is a very, very large engine change. Yes,
> it does not touch the Zend engine itself, but it adds a large amount of new
> code that is close to the engine. People doing engine changes will need to
> modify it too (thus it is quasi part of the engine, even if it lives in a
> separate directory). All existing core devs will have to study and
> understand the code. All new developers have an additional piece of very
> complex code to study before they can start making core changes.

Which arguable core devs should have been doing for years but weren't.
The issues you need to be aware of with ZO+ aren't any different from
what you need to be aware of with any opcode cache and that has been the
cause of the big lag between new PHP releases and support from opcode
caches. Getting everyone on the same page with a single de-facto
standard opcode cache is going to be a huge win and the sooner we can
get there, the better.

-Rasmus