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
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
