Slightly brambly thoughts... I think (imho) the PHP6 hype in user land died down long ago after it became obvious it wouldn't materialise any time soon. It would be nice to see 6 to appear if only to break the (apparent) deadlock that the Unicode stuff brought on(I realise this is not enough justification by itself) What will this mean to all the Hosting providers etc who are still finishing long running 4->5 or 5.x -> 5.3 migrations? Will they resist change more because it looks like a bigger change regardless of the underlying code? As they provide installs/hosting for what I can guess to be a huge amount of the PHP's actual users is it factor that's worth considering
I realise this is a Friday afternoon category comment but it can't wait.. Think of all of those PHP6 books that will be reduced to near junk status in swift branch/commit action And as a bonus -----Original Message----- From: Jani Taskinen [mailto:jani.taski...@iki.fi] On Nov 25, 2010, at 1:46 PM, Patrick ALLAERT wrote: > 2010/11/25 Jani Taskinen <jani.taski...@iki.fi>: >> Who says it has to be 5.4? People seem to be a bit fixated on the version >> there. > > I'd like to know too... > >> Major BC breaks just means the version released from trunk is 6.0. And it's >> just a number. Big number, but still just a number. > > Well, such a change tends to create a big buzz, without mentioning > stuff like certifications, trainings,... This is a joke, right? > We should avoid creating a virtual PHP 6.0 which will contain all the > BC stuff while all features appears in 5.x. > By doing so we will keep some shit in 5.x forever and won't have > anything appealing enough to migrate to 6.0 ..or have something really new and interesting in PHP 7.0.0. The big version number change is reserved for BC changing stuff, not just for "fancy new stuff". --Jani -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
