Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26483
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.184.226 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=Npdi1zsumltYO8ziBVHQh64ViS+tq7oqcQhV4Gt912NC8gMZUbyBD4mIuHBWAch4tXncpRwgaX0IGPM05a8SOezT8hTO0CBkYbkgxGgtF4tUq6rWz7mVTChyDbE7N41XDAaaMfOrMib3d7c5WtTCmwGBiRrhlU6RFOjZPh9OP7U=
In-Reply-To: <4554C2C7.9070502@caedmon.net>
References: <4554AE0D.4080600@caedmon.net> <D268FFAD-6916-4EDE-9511-31F5BC774318@prohost.org> <4554B9B5.5090305@caedmon.net> <DA611470-FC2C-48DE-AE6B-29EC4554A298@prohost.org> <4554C2C7.9070502@caedmon.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <A5026B89-540C-4441-98B8-DAA86CCA2B84@prohost.org>
Cc: internals <internals@lists.php.net>
Content-Transfer-Encoding: 7bit
Date: Fri, 10 Nov 2006 13:31:40 -0500
To: Sean Coates <sean@caedmon.net>
Sender: Ilia Alshanetsky <iliaal@gmail.com>
Subject: Re: [PHP-DEV] Namespaces in PHP 6 - ++$take
From: ilia@prohost.org (Ilia Alshanetsky)


On 10-Nov-06, at 1:19 PM, Sean Coates wrote:

>> PHP 6 is not yet out and probably won't be production quality for  
>> quite
>> some time. Which means that migration to it en mass is probably not
>> going to happen this decade :-).
> <snippitysnip/>
>
> I'm not talking about forcing everyone to use namespaces tomorrow. I'm
> trying to plan for a future where there's a sensible way to avoid  
> symbol
> collision.

Since day one there was a sensible way to do, prefixing, but for  
whatever reason (and let's not get into that discussion) many people  
had not which is why we are having this problem today.

> As for everyone developing on PHP $release-1 until 50% market
> saturation, I believe that to be the case in widely-distributed PHP  
> apps
> (such as FUDForum), but you seem to be forgetting about the large  
> number
> of PHP applications that are developed for internal use. I don't  
> know of
> anyone currently using PHP 4 to develop new PHP apps unless they're  
> for
> external distribution.

I was not referring to just the distributable applications, I know of  
many companies and people who develop internal software that's PHP4  
only as they have no plans to move to PHP5. There is also a large  
number of ISPs providing exclusively PHP4 solutions, which  
effectively forces their client base to stick to PHP4. You also  
forget that a larger number of PHP developers started their  
development by looking at other people's code and using that as a  
base. Given that the base is predominantly PHP4 they tend to continue  
using PHP4.


Ilia Alshanetsky