Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30279
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain e-novative.de from 85.214.26.34 cause and error)
Message-ID: <4678C9D7.1030709@e-novative.de>
Date: Wed, 20 Jun 2007 08:31:51 +0200
Organization: e-novative GmbH
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Lukas Kahwe Smith <mls@pooteeweet.org>
CC: Rasmus Lerdorf <rasmus@lerdorf.com>, 
 Ilia Alshanetsky <ilia@prohost.org>,
  internals@lists.php.net
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> <21277473-1502-4F7E-9C3B-BE42C50DD7CB@prohost.org> <467839D0.2020301@lerdorf.com> <46784B95.4000102@pooteeweet.org>
In-Reply-To: <46784B95.4000102@pooteeweet.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: stefan.priebsch@e-novative.de (Stefan Priebsch)

Hi list,

IMHO PHP6 might need more new features to attract developers to migrate
their code / write new code for PHP6. Unicode support is great for those
who need it, but is likely to cause work for those that "just have to
live with it". Nobody likes to so extra work, and it's hard to get
managers to pay for refactoring and updating software without
visible/measurable benefit. Especially if the new version it going to be
slower, it's tough to push it through.

Namespaces in PHP 6.0 might be a very interesting feature for many
developers. Currently, it seems that unicode will be main thing, which
might result in lots of developers not care about it and just wait for
namespaces or another feature they need in 6.1 (or whenever).

Regarding the BC break: maybe breaking BC can be cleverly used as a
marketing statement. "We have cleaned up PHP, to get rid of some sins of
the past". If users do not upgrade because there is just one or two
small issues that require them to put work in their existing code, then
why keep BC?

Those who are planning to upgrade to PHP6 will always have to put in
some work into their code, or at least test it on PHP6.

Those who stick with older versions do not really care wether the new
version breaks BC "just a little" or "really a lot" - they are not going
to touch their existing code anyway and stick with older PHP versions.

Kind regards,

Stefan

-- 
 >e-novative> - We make IT work for you.

 e-novative GmbH - HR: Amtsgericht München HRB 139407
 Sitz: Wolfratshausen - GF: Dipl. Inform. Stefan Priebsch

 http://www.e-novative.de