2 ms·
If you read the article, it's full of notes about "this was fixed in 5.4" or whatever. A decent chunk of the remainder has been fixed in the 7.x series, and so
by Lazare 7y ago
If you read the article, it's full of notes about "this was fixed in 5.4" or whatever. A decent chunk of the remainder has been fixed in the 7.x series, and some of the remainder is slated to be solved in the (as of yet, unreleased) 8.0 version.
Just scrolling through at random:
> A function’s return value can’t be hinted.
But of course, this has been incorrect for years. The next was fixed in 5.3, the next two be fixed in 7.4, the next was fixed in 5.4, etc., etc. Which is fine; it's an old article, and one which was deeply influential on PHPs development, but it's completely false to suggest that "literally every single thing in that post still holds true". Many are outdated.
- richardwhiuk 7y agoI agree some of it has been fixed - but definitely not all of it, or even anywhere close. Some highlights of why I wouldn't rely on PHP in my stack: - A fair chunk of phpsadness is still unfixed - e.g. https://bugs.php.net/bug.php?id=49664 https://bugs.php.net/bug.php?id=49664 where recursing too much producing a segfault is Not A Bug. - PHP's release machines were compromised. Let's not worry who downloaded it. http://news.php.net/php.internals/77695 http://news.php.net/php.internals/77695 - PHP 6. There's no hope of making PHP work in Unicode, ever. It's like Python 3, except half way through, they went 'let's not even bother'. - The rebuttal elsewhere on this thread points to the very problem in the PHP community: >> PHP’s one unique operator is @ (actually borrowed from DOS), which silences errors. > Yup. I find it very useful on the unlink() function which will raise an error if the file you're trying to delete doesn't exist. That just demonstrates that unlink is broken! PHP's error handling is some horrible collection of C, C++ and just spamming stderr.