Rightly or wrongly, many in our community see Perl 6 as the definitive example of vaporware. But what about PHP 6? This release was first discussed by the PHP core developers back in 2005. There have been books on the shelves purporting to cover PHP 6 since at least 2008. But, in March 2010, the PHP 6 release is not out - in fact, it is not even close to out. Recent events suggest that PHP 6 will not be released before 2011 - if, indeed, it is released at all.

He talks about features that were supposed to disappear in PHP6 (with some of them making their way into PHP 5.3) including the Unicode support the language needs more and more. He mentions how the development has stalled out a bit recently but has been spurred back to life when major decisions were made to get away from a PHP 5.4 branch and move back to PHP6.

Be sure to check out the great comments on the post from other PHP developers from all around the web.

If you enjoy this post, please consider subscribing to LWN for more great articles.

Posting in the full realization of the futility of doing so, there's some PHP bashing (as usual) happening on reddit at the moment: PHP vs Python - the real difference, brought on by this mildly amusing image. While I can accept the points - technically it's actually much harder in handle errors uniformly in PHP and the community is less rich in computer scientists than Python - the corresponding flame war on reddit manages to miss a different point, which is easiest expressed in code.

He gives two sample scripts and asks what the real differences are. He answers his own question by way of saying that what matters between the two is how they're deployed (when it comes to error reporting):

Because PHP "resets" after each request ( see here or for much more detail here ) it's actually not always necessary to handle errors explicitly'"assuming there's not something fundamentally "broke" about your code and it's some kind of runtime error (e.g. db is down), it's often enough to just ignore the problem and wait for the system to "right itself" - nothing is going to leave PHP in a state it can't recover from.