3 ms·
> Well, after a little over six years of development, we discovered that we were never going to see a PHP 6 at all. Having seen how long Perl 6 had taken, and h
by TazeTSchnitzel 12y ago
> Well, after a little over six years of development, we discovered that we were never going to see a PHP 6 at all. Having seen how long Perl 6 had taken, and how long PHP 6 was taking, the number 6 is associated with failure. So they cancelled PHP 6 and voted to change the name to PHP 7.
Uh, what? Did the author do the most basic of research?
PHP 6 was a real thing, a development branch. But it dragged on for years.
Due to delays, they made an interim release in the 5.x series, PHP 5.3. It backported some stuff from 6.
Eventually, PHP 6 was killed off because it just wasn't going to work. So they made another 5.x release, PHP 5.4, backporting more stuff from 6, and adding some other features.
After that, with PHP 6 dead and gone, work focussed on the PHP 5.x series again. So out came PHP 5.5 (2013) and PHP 5.6 (2014).
During this time, some people did some experiments and realised it was possible, by breaking internal (not userland) compatibility, to greatly improve PHP's performance. This project became phpng. Since it would break so many (internal) things, they decided that if it should be merged into PHP, it needed to go into a new major version.
It was after this that the ridiculous version number vote was held. I don't see why we ever had that debate, really. PHP 6 was a thing and was killed off, re-using the version number was silly. Anyway, the number chosen was PHP 7.
Fast forward to the present day: PHP 7 has gone into feature freeze and should be released in a few months. Alongside the performance improvements of phpng, it has some other new features developed independently, and includes a few deliberate backwards-compatibility breaks.
tl;dr: the time line goes: 5.2 release, work begins on 6.0, 5.3 release, 6.0 killed off, 5.4 release, 5.5 release, 5.6 release, 7.0 in development.
Edit:
> JIT to the Zend engine
...what? No, PHP 7 does not have that.
> Asynchronous IO and functions
...PHP 7 doesn't have that either?
> Standalone Multi-threading Web Server (HHVM)
...huh?
> phpclasses.org
Oh, so that's why the author is so confused.
- meritt 12y agoPHP haters are notorious for using blatantly incorrect or horribly outdated information. Correct PHP 7.0 changes: https://wiki.php.net/rfc#php_70 https://wiki.php.net/rfc#php_70
- smsm42 12y agoThe problem with this is since they despise PHP they don't even bother to learn the correct information about it. Which means what they despise is entirely the product of their own imagination, and for anybody informed it sounds completely laughable. Unfortunately, they are not getting called out on it as frequently as they should be and the cycle of misinformation continues.
- McGlockenshire 12y ago> Oh, so that's why the author is so confused. So for anyone wondering about this, phpclasses was the answer to PEAR, which itself was trying and failing to be CPAN. PEAR ended up being laughable and underwhelming, while phpclasses ended up being a breeding ground for some of the worst PHP code on the planet. Nobody should be using it and anyone pointing to anything on it as a good example should be laughed at. Meanwhile, the article author probably needs to read this slide deck from the PHP6 team explaining exactly where the breakdown occurred: http://www.slideshare.net/andreizm/the-good-the-bad-and-the-ugly-what-happened-to-unicode-and-php-6 http://www.slideshare.net/andreizm/the-good-the-bad-and-the-... The postmortem starts on slide 60, but the rest is worth reading. It had nothing to do with second system syndrome at all.
- serve_yay 12y agoSounds like a disaster. Also funny how anyone discussing PHP's flaws gets met with "oh THERE'S your problem, you decided to use this terrible awful piece of shit thing instead of not doing that". Well why in the hell was that an option in the first place?! The golf course is full of landmines, and if you bitch about how shitty it is to step on one, nobody goes "yeah it sucks how this course is full of landmines", you're just an idiot because you stepped on one, like an idiot.
- stephenr 12y agoSo you're suggesting that the PHP community at large, is somehow responsible for a single site, that gives bad advice, has bad information, etc. What exactly is your solution? a SWAT raid to take down this travesty of technology?