Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26325
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.162.192 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender;
        b=CW2Fpdy8s2qB5+bGgxH2wmfbaIThI7l8pg/oGVRXG2O6BVLmrO7MQ2Dbq1fdZCfYFgmfM/jYn0PIaTRvqmW6DxoeXtvAh1Q15RFeC7fGJdPERGAL9F7MavlbzwRZVl24LdVCcBc6gWC98lvcoaX6vbRcZpPt/kOwEHOyStCyDZc=
In-Reply-To: <454CBD65.5040205@cschneid.com>
References: <005e01c6ff82$e6092c30$ec01010a@intranet.db> <2FAA3BA3-283C-445D-9648-70C207FF2251@prohost.org> <454CBD65.5040205@cschneid.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <B990B08B-20E3-41FD-BA54-A8F78443B572@prohost.org>
Cc: internals@lists.php.net
Content-Transfer-Encoding: 7bit
Date: Sat, 4 Nov 2006 13:34:55 -0500
To: Christian Schneider <cschneid@cschneid.com>
Sender: Ilia Alshanetsky <iliaal@gmail.com>
Subject: Re: [PHP-DEV] New Datetime class problem
From: ilia@prohost.org (Ilia Alshanetsky)


On 4-Nov-06, at 11:18 AM, Christian Schneider wrote:

> Ilia Alshanetsky wrote:
>> Avoid common namespaces and you'll make your application futureproof.
>
> I'm still wary of this approach because it puts the burden on 99%  
> of the code to be written (applications) instead of a small,  
> controllable subset (core and libraries).

Translation: blame other people...

>> When developing a distributed application it is always a good idea  
>> to prefix functions/class names with app name or some acronym to  
>> avoid overly long names. The way things are going you are going to  
>> see more and more classes being introduced by "core" PHP as well  
>> as the growing
>
> ... which brings us back to the discussion of namespaces and which  
> one core classes should use ;-)

The language should ALWAYS have the best names possible to simplify  
development, because that means convenience for majority of users. No  
matter how popular your app, PHP, the language is still hundreds if  
not thousands of times more popular and as such needs of many  
outweigh needs of the few.

>> number of PECL extensions out there and I am not even going to  
>> mention the thousands of libraries out there.
>
> Those are less of a problem because you don't have to include them  
> if you don't want to.

You can use old PHP too, or modify the source code, it is "open  
source" after-all.

Ilia Alshanetsky