Newsgroups: php.apc.dev,php.internals
Path: news.php.net
Xref: news.php.net php.apc.dev:190 php.internals:43176
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.180 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:reply-to:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        b=vnvX6aiQQ1twT+WGNyl+CzZUY0EK7TVPCo/vas+xLKNiDVi424nXs4X3ORPpwT9ToP
         hJbIrVQoBGwxML9ZVsjTc8SUcLfSpiItu+VzZn+RSNAHV5lBbmYuA0cPPXaVcXBzyBRA
         VwXFj4mLodhjrbzKpODckFs+xtL4WA4kzStdk=
MIME-Version: 1.0
Sender: surreal.w00t@gmail.com
Reply-To: viroteck@viroteck.net
In-Reply-To: <2E.38.44668.710A6A94@pb1.pair.com>
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>
Date: Thu, 26 Feb 2009 14:07:09 +0000
Message-ID: <b19eae4e0902260607u10094cb5wb635d705e9a0f03@mail.gmail.com>
To: Rodrigo Saboya <rodrigo.saboya@bolsademulher.com>
Cc: apc-dev@lists.php.net, internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] APC/PHP Lazy Loading
From: viroteck@viroteck.net (Robin Burchell)

On Thu, Feb 26, 2009 at 1:58 PM, Rodrigo Saboya
<rodrigo.saboya@bolsademulher.com> wrote:
<snip>

> 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.

It's probably also worth noting that in a lot of cases, you really
*won't* use a lot of what you load, at least initially. If you're
working in an OOP fashion, for example, you won't use every method at
once on an object, but you're still going to have to pull the whole
object in to use it.

If you're writing functional code, the same applies: there will often
be some generic parts of stuff that you won't use for *every* request
that you still won't split out into a seperate file simply because
they are *often* used..

I think I'd have to guess that around 40% of the code I load gets used
on a single request, but that is because of the aforementioned problem
of using classes. It's not that big a worry to me, because I use APC
to lessen the hit, and thankfully(? :)) I don't have thousands of r/s,
just a few hundred.

Seems like a good change to me.