Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65389
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.212.49 cause and error)
Message-ID: <5107D429.60001@lerdorf.com>
Date: Tue, 29 Jan 2013 05:52:41 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Clint Priest <cpriest@zerocue.com>
CC: "internals@lists.php.net" <internals@lists.php.net>
References: <5d21b42656d49b4a71d9f808541bd745@mail.gmail.com> <252ADB1A-2660-4A45-B859-B92DA2C8B8D8@gmail.com> <CAAyV7nEW_tHNObKcH3knin0-GPXakUiv1KoHYzjHiOJ1EB=wRg@mail.gmail.com> <5107CEEB.9080003@zerocue.com>
In-Reply-To: <5107CEEB.9080003@zerocue.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Integrating Zend Optimizer+ into the PHP distribution
From: rasmus@lerdorf.com (Rasmus Lerdorf)

On 01/29/2013 05:30 AM, Clint Priest wrote:

> 2) Isn't APC the standard?  Is it in such bad shape it is not even being
> considered any longer?

As it currently stands from a developer participation standpoint it is
not viable. I outlined the issues in a previous post.

You also have to take into account that most sites can't actually move
to the next release of PHP until APC is stable with it. So effectively
the PHP 5.4 release didn't happen until APC 3.1.13 in September 2012
which was a full 6 months after PHP 5.4.0. I don't foresee this getting
any better for PHP 5.5.

In order for PHP releases to actually mean something this is a problem
we have to fix. I honestly don't care which opcode cache implementation
we base a core version on, what I care about is developer buy-in. Dmitry
and Stas being familiar with the code already outnumbers the number of
active core devs working on APC today.

I understand some of the skepticism and hurt feelings around this from a
few old-timers, but let's move on and see if we can finally push out a
release with solid opcode caching right at the release date. From my
perspective anything up to a 6-month delay would beat the current situation.

-Rasmus