Zeev Suraski wrote:
I think you have some good ideas in that list, and some less good ideas. I'm worried about the wholesale mode that internals@ switched into, the almost unanimous "YES!" response, and the overall feeling that suddenly with 6.0 breakage comes without a price. That goes counter to our key design goals in the Unicode support, which were work-as-if-nothing-happened when unicode support is disabled.
Then don't call it "6.0". "5.2" or "5.5" would be OK. Unicode support is cool but calling a release "6.0" just because of that looks a litte bit like "hey perl, we reached the 6.0 before you" while everyone knows that PHP is from the internal point of view still far behind Perl 6.
Remembers me a little bit of the "browser war" in the beginning of this decade.
Every new major version gives PHP the chance to break up with things and a drastic cleanup would be very nice in my eyes.
Sebastian -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
