Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65377 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50050 invoked from network); 29 Jan 2013 13:27:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jan 2013 13:27:43 -0000 Authentication-Results: pb1.pair.com header.from=kalle.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=kalle.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.174 as permitted sender) X-PHP-List-Original-Sender: kalle.php@gmail.com X-Host-Fingerprint: 209.85.128.174 mail-ve0-f174.google.com Received: from [209.85.128.174] ([209.85.128.174:45875] helo=mail-ve0-f174.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 01/58-10721-E4EC7015 for ; Tue, 29 Jan 2013 08:27:43 -0500 Received: by mail-ve0-f174.google.com with SMTP id c13so260173vea.19 for ; Tue, 29 Jan 2013 05:27:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=kjksmK9kX+/MBM2fAN0FAsajpFj1efPfHxCyeOXf1aI=; b=PHVen9fky+zYz+sAGIroLJs8nJWYybdAwkPiF2XqfkAri4G2At4aYnjrjYP9nyqcZz Ti3im37GAhoAN+Pp6i43e3aMajcSKiTRI4UgaQzV/uLYts+UEHPSzuoZ1QtMzJKA5wP0 8NLL7/uGu64tn6PMnhUPzt3GihWDca+B55bPhzGrWQu4YfECLe9c7msIrKILxSVWK0BA K0kNAPpLvzRNOJz/weOwqNSAj6/ZoAPvSzaTzvY/gWDdAAORk1xFWqLieT9jgx5LB4uk cfsFAr/0TNVKI35H01U9oLHz2moyqw1tpGdBYJQWMcHATKz1BMdkVyEoM7bJz8zNGIAg NPog== MIME-Version: 1.0 X-Received: by 10.220.149.82 with SMTP id s18mr961594vcv.14.1359466060306; Tue, 29 Jan 2013 05:27:40 -0800 (PST) Sender: kalle.php@gmail.com Received: by 10.58.180.10 with HTTP; Tue, 29 Jan 2013 05:27:40 -0800 (PST) In-Reply-To: <5d21b42656d49b4a71d9f808541bd745@mail.gmail.com> References: <5d21b42656d49b4a71d9f808541bd745@mail.gmail.com> Date: Tue, 29 Jan 2013 14:27:40 +0100 X-Google-Sender-Auth: pV4vQEAP33g9MsxKGuMuhVEjxDU Message-ID: To: Zeev Suraski Cc: internals@lists.php.net Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Integrating Zend Optimizer+ into the PHP distribution From: kalle@php.net (Kalle Sommer Nielsen) Hi Zeev 2013/1/29 Zeev Suraski : > In parallel we=92re in the process of prepping the source code for > independent public consumption, which I hope we can be done with by the e= nd > of next week, hopefully sooner. I'm sorry, but I don't see why we out of a sudden should consider adding a Zend product to the core, over that we got already, yes I'm pointing in APC's direction, although it is in PECL. I'm not trying to bring in this skepticism here because I'm, a previous APC dev, but mostly because I do not think this is the right move. Why? Because we tried to push APC from PECL into the Core since early 5.x, although I've only been around since just before 5.3a1, I remember how we were all focused on putting APC into the Core rather than a non php.net project (like XCache, eAccelerator, ...), where many of the core developers have invested much time in promoting APC, and tried to fix some of the issues it have had. Moving APC into the core was against some people's PoV because they thought it would be enabled by default, which it wouldn't be at all. I am very strongly against this move if its approved (not the actual RFC), but how an outside product suddenly deserves a spot in the core over our own code, by that I mean folks that does not work for Zend, but have contributed the code to php.net, I think that is highly controversial. --=20 regards, Kalle Sommer Nielsen kalle@php.net