Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:66327 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 8451 invoked from network); 28 Feb 2013 14:01:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Feb 2013 14:01:35 -0000 Authentication-Results: pb1.pair.com smtp.mail=ircmaxell@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ircmaxell@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.175 as permitted sender) X-PHP-List-Original-Sender: ircmaxell@gmail.com X-Host-Fingerprint: 209.85.128.175 mail-ve0-f175.google.com Received: from [209.85.128.175] ([209.85.128.175:60131] helo=mail-ve0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DC/D3-17375-D336F215 for ; Thu, 28 Feb 2013 09:01:34 -0500 Received: by mail-ve0-f175.google.com with SMTP id cy12so1831944veb.34 for ; Thu, 28 Feb 2013 06:01:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Xz547kcUZx67lFbcMft4IokATdXSFOVdQJd0FEqv4b8=; b=u+XeTHNw4SrDN9eOzrItrRyQuXsoiO5Q3zPJpWtWOzVJ6W+p+neNdZ5CxDMaTlg6p7 BJP/I1npQX73keI0xSDgzkL0KL1+vBug1qW8l/424SqplBxdNC4DYrxvHxaLkF8TVY3j UUR3UOb6gIruIO69oKsa3+TQKrBbnUruX+V8wZhusHCLTAedJmiZ5YtpSafpOThTzgzJ dSi2LC2wy29yErVAP9bVOXmP1nM9SgJBICMN9XkF6BhdhRkG8g/pVrkZvZV4gRzaJCOT nYQEhKDEY9vLVC6su1XilaSeuigr2N+F9sV9f27F4GFod3W+IfxBkeXhmGfF3Hj0ttD4 tLyg== MIME-Version: 1.0 X-Received: by 10.52.19.200 with SMTP id h8mr2204294vde.60.1362060091042; Thu, 28 Feb 2013 06:01:31 -0800 (PST) Received: by 10.58.56.137 with HTTP; Thu, 28 Feb 2013 06:01:30 -0800 (PST) In-Reply-To: References: <435a322ccb14090d3bcf6bf8a110396d@mail.gmail.com> <512E7870.7010208@lerdorf.com> <0b8c20490dae9ecb9f9cd4a77cf47796@mail.gmail.com> Date: Thu, 28 Feb 2013 09:01:30 -0500 Message-ID: To: Ilia Alshanetsky Cc: Zeev Suraski , Pierre Joye , Ferenc Kovacs , Rasmus Lerdorf , PHP Developers Mailing List Content-Type: multipart/alternative; boundary=20cf307ca04ce3e98504d6c953d6 Subject: Re: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP distribution From: ircmaxell@gmail.com (Anthony Ferrara) --20cf307ca04ce3e98504d6c953d6 Content-Type: text/plain; charset=ISO-8859-1 Ilia, On Thu, Feb 28, 2013 at 8:54 AM, Ilia Alshanetsky wrote: > Zeev has an excellent point here, my own research shows that 5.4, a > year after release had somewhere in the 2% adoption rate. The major > reason being is the lack of a stable, production ready op-code cache. > To release 5.5 without a good solution for that problem, would not > make the situation better, if anything it would make it very > intimidating to users to jump 2-3 versions directly to 5.6. Thus > leaving us with a massive user base running legacy, unsupported > versions containing unresolved bugs and vulnerabilities. Something, > which I don't think would be a very good thing for the future of PHP. > To be fair, the 5.5 situation without pulling in ZO+ is NOT the same as 5.4 was. Today, right now, there exists at least one stable open source opcode cache. 5.4 had none for many months after release. So I'm not sure if the same pressures exist. The discussion now is if we delay 5.5 to spend the time pulling it in core. But either way (in core or not), ZO+ is open and working on 5.5 alpha. So we could skip the core import, and just ship it today as gold, and it would be adoptable straight away (unlike how 5.4 was). > Ultimately, I think it is better to wait a month or two (if that is > what it takes) and have a solid release people can safely upgrade > their production environments to, rather than strictly adhere to a set > release cycle and delivery a partial solution. That's the thing though, it wouldn't be a partial solution. It would be exactly where 5.2, 5.3 and 5.4 are today, with the addition of several highly wanted features. I'd rather delay 5.6, and do a deeper integration into the engine. Then at least there's something to gain by pulling it into core, rather than just having it be a compile-time-flag as opposed to a pecl installation (which doesn't buy us *that* much)... My standpoint at least... Anthony --20cf307ca04ce3e98504d6c953d6--