Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30273
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain prohost.org from 64.233.166.176 cause and error)
In-Reply-To: <46783212.4020900@lerdorf.com>
References: <1181829227.3478.3.camel@localhost.localdomain>	 <7d5a202f0706141844l3c75b556hdbecbcd5a43747c9@mail.gmail.com>	 <4671F184.2020401@lerdorf.com>	 <6sof73dj69ldpspfc5ukrc58qr9ckbin2b@4ax.com>	 <4677E7B1.2080305@lerdorf.com> <fe05d1540706190808o1d9305b3td74edd6d1c75c97@mail.gmail.com> <4677F5FB.1070206@lerdorf.com> <4678252F.2050803@sci.fi> <46783212.4020900@lerdorf.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <21277473-1502-4F7E-9C3B-BE42C50DD7CB@prohost.org>
Cc: jani.taskinen@iki.fi,
 internals@lists.php.net
Content-Transfer-Encoding: 7bit
Date: Tue, 19 Jun 2007 15:59:31 -0400
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: ilia@prohost.org (Ilia Alshanetsky)

Sorry to interject, but just a quick slightly off topic note.

In your earlier e-mail you've said that

-----------------

I actually don't have a problem with 95% of PHP 6 installations turning
off Unicode support and this being the default setting for ISP's.

Full Unicode support in an application is a big commitment and it will
take quite a bit of work.  I just don't think that many people will
invest the time and effort into doing this, but at the same time there
will be large applications and services that have full control over
their server settings that will make use of it.  Think Flickr, Yahoo,
Facebook, etc.

-----------------

Since 95% of installations will not be using PHP6 (php6 without  
unicode is pretty much a slower version php5) for whatever reason,
we need a common version for the other 95%. I think it is inevitable  
that there will be 2 continually developed versions of PHP out there,  
one for people who need unicode support in the way that is envisioned  
by PHP6 and one for people who don't need it.



On 19-Jun-07, at 3:44 PM, Rasmus Lerdorf wrote:

> Jani Taskinen wrote:
>> Rasmus Lerdorf wrote:
>>> Uh, this was agreed upon by everyone involved in the design of the
>>> Unicode support.  So saying I am the only one is extremely  
>>> misleading.
>>> I may be the only one explaining why the decision was reached,  
>>> but I am
>>> certainly not the only one in favour of it.
>>
>> Yesterday's decisions don't necessarily apply today. ;)
>> (to be "agile")
>
> Fair enough, but it would be nice if the folks involved in the  
> decision,
> including yourself would then clearly state their reasoning for  
> making,
> or at least supporting, the decision in the first place and then  
> explain
> what has changed to make you change your mind.
>
>>> By not providing it, we ensure that a large number of people will  
>>> not
>>> move to PHP 6.  At least by providing it we give ourselves a  
>>> chance.  I
>>
>> Yes, you assume that this happens. I've got a hunch too that there  
>> will
>> be more PHP 6 user's than there ever where with PHP 5 by just  
>> thinking
>> how many asian, arabic, etc. people there are in the world..lot more
>> than western anyway.
>
> It comes down to predicting the future.  Whichever way we go, the
> decision is going to be second-guessed.  If we have critical mass  
> for a
> clean BC break, then I am ok with it.  For me personally it would make
> things a bit easier, but I think it would be a long long time  
> before we
> saw any large hosts out there switch to a PHP 6 that can't run common
> PHP 5 apps.
>
> -Rasmus
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

Ilia Alshanetsky