Newsgroups: php.apc.dev,php.internals Path: news.php.net Xref: news.php.net php.apc.dev:196 php.internals:43206 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60227 invoked from network); 27 Feb 2009 02:38:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Feb 2009 02:38:24 -0000 Authentication-Results: pb1.pair.com header.from=ron@Opus1.COM; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=ron@Opus1.COM; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain Opus1.COM designates 192.245.12.8 as permitted sender) X-PHP-List-Original-Sender: ron@Opus1.COM X-Host-Fingerprint: 192.245.12.8 Viola.Opus1.COM OpenVMS 7.2 (Multinet 4.3-4.4 stack) Received: from [192.245.12.8] ([192.245.12.8:4695] helo=Viola.Opus1.COM) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 91/87-30584-D1257A94 for ; Thu, 26 Feb 2009 21:38:24 -0500 Received: from [192.168.1.6] ([76.105.138.13]) by Opus1.COM (PMDF V6.2-X27 #9830) with ESMTPSA id <01N5YSJUCIU096UX12@Opus1.COM>; Thu, 26 Feb 2009 19:38:18 -0700 (MST) Date: Thu, 26 Feb 2009 18:38:16 -0800 In-reply-to: <2E.38.44668.710A6A94@pb1.pair.com> To: Rodrigo Saboya Cc: apc-dev@lists.php.net, internals@lists.php.net Message-ID: MIME-version: 1.0 X-Mailer: Apple Mail (2.753.1) Content-type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-transfer-encoding: 7bit X-Gpgmail-State: !signed References: <49A097FE.10205@tekrat.com> <633918AD-16DE-4B34-A76E-E90A21E325B3@opus1.com> <49A0F6D6.3080605@tekrat.com> <6A41B9D3-7312-49F3-A4B0-C5D6DC23AF9D@Opus1.COM> <2E.38.44668.710A6A94@pb1.pair.com> Subject: Re: [PHP-DEV] [RFC] APC/PHP Lazy Loading From: ron@Opus1.COM (Ronald Chmara) On Feb 26, 2009, at 5:58 AM, Rodrigo Saboya wrote: > Ronald, I think you are overreacting a little bit. It may be that > proper written could would get no benefit from this patch since it > would not load unneeded code and this patch ends up speeding up > environments where such "correct" loading isn't done. I don't think > that's a reason to disqualify a feature that brings benefits with > no significant drawbacks. > > For the average PHP programmer, the language will simply "get > faster". That can't be bad in any way. It doesn't encourage you to > write bad code, it just doesn't kick you in the nuts when you do. Sold. (The best arguments are always the short ones). As I said: "I'm trying to raise a token flag of discussion/ resistance", but nobody in the discussion seems to have found any really important downsides, yet, with only me raising *any* sort of flag (though I admit it's not much of one). :) -Bop