Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34890
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.184.225 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=ti0bkTlIvuybiRowL+xXnjOgy8cpCIxP2gKOfWKo5uDJxjauTbP+qpgVHKgVl9FU8IIA9PLHaWqciI7vpLEDqdsCRzCjI3Z21ku7ViieylJv1YwVz88xpWL5eCPHP9q6n6jnUY550Se7YXnvZHIDzVrM90guvtCxC1rsGO6h2Pk=
Message-ID: <e2e02fe0801231114vb4c7a15r6d037867972ad4e5@mail.gmail.com>
Date: Wed, 23 Jan 2008 12:14:20 -0700
To: ceo@l-i-e.com
Cc: php-dev <internals@lists.php.net>
In-Reply-To: <38791.98.193.37.55.1201055548.squirrel@www.l-i-e.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4794AE48.20005@daylessday.org>
	 <38791.98.193.37.55.1201055548.squirrel@www.l-i-e.com>
Subject: Re: [PHP-DEV] why we must get rid of unicode.semantics switch ASAP
From: chrisstocktonaz@gmail.com ("Chris Stockton")

I partially agree, I have been watching this discussion and it's funny
how we have such a class of high end developers saying to break old
PHP code. But, the majority of the success of PHP is not due to this
small class of high end developers, it's due to it's availability in a
shared hosting environment, and the ease of use for beginners, and the
oodles of fairly poor quality code that is easy to copy and paste onto
peoples websites.

Look at the adoption of php4, many webhosts haven't even updated to
PHP5 completely due to things like register_globals and small
backwards compatibility breakage. The list of problems is small and
correctable, if you give system engineers at all of these hosting
companies the choice of A. Upgrade to php6 and drive support calls
through the roof, or B. Stay at PHP4/5 for eternity until a more
(insert your complaints / rants here) language comes along to dethrone
PHP.

Problem is, PHP has been built to great success based on it's early
foundation, but now a group of high class developers want it to be
more then PHP was built onto. You will sacrifice it's success if
backwards compatibility is not just, broke, but obliterated. Why
change PHP's philosophy? Keep it easy for the new user, keep it
successful, and make me work a little more when I want to implement my
"high class" development methodologies. I don't mind, I do it already.

I write this as a "high class" developer.

-1

-Chris

On Jan 22, 2008 7:32 PM, Richard Lynch <ceo@l-i-e.com> wrote:
> On Mon, January 21, 2008 8:38 am, Antony Dovgal wrote:
> >
> > 6 reasons why we must to get rid of The Switch ASAP
> > ----------------------------------------------------
>
> I was +1...
>
> Until folks started posting that old PHP scripts won't run as-is in
> PHP 6?...
>
> That's just daft...
>
> When my webhost upgrades to PHP 6, I need all my old scripts to just
> keep on chugging away, as much as possible...
>
> I really think we're stuck with the default "string" being an
> old-school binary string, unless you want to lose a LOT of users in a
> hurry, or have PHP 5 stick around forever and ever.
>
> --
> Some people have a "gift" link here.
> Know what I want?
> I want you to buy a CD from some indie artist.
> http://cdbaby.com/from/lynch
> Yeah, I get a buck. So?
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>