3 ms·
> 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
by McGlockenshire 11y 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 11y 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 11y 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?