On 06.07.2007 14:04, Lukas Kahwe Smith wrote:
To me it boils down how we want to maintain the "fork":
1) PHP5 and PHP6
2) PHP6 unicode off/on (with PHP5 in maintenance mode)
Considering that people will not jump on PHP6 immediately anyways, I
think 1) is more realistic, if we make best efforts to back port new
features to PHP5, but still require that new features go into PHP6
first. Some features might not get back ported and that is a somewhat
unfriendly nudge towards PHP6. So it goes.
I tend to agree with this POV more and more.
Especially considering this:
--
Rasmus Lerdorf wrote:
So yes, the only real customers for this full Unicode mode in PHP 6 are
going to be the folks that have full control over their servers and
their software which will likely limit it to hosted services and exclude
large PHP software packages that will necessarily need to be written to
be portable.
--
If we admit that we release a special PHP version for a very limited set
of users then keeping that On/Off switch makes no sense to me.
And it's not about choice, customers DO have a choice - either it's PHP5 (which will
still be there for the next 10 years at the very least) or PHP6 aka Unicode PHP.
You don't by a Porsche if you need a taxi, why would you install PHP6 if you
don't need Unicode?
New features? Let's just agree that we can (and definitely will) backport all the fancy looking
new features from PHP6 to PHP5 and both these branches can live together happily.
This way the PHP6 code base stays lean and people can realistically code
against PHP6. Hosters will hopefully offer both PHP5 and PHP6. I doubt
that many hosters would be interested in offering 3 versions at once
(PHP5, PHP6 unicode on/off).
--
Wbr,
Antony Dovgal
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
