4 ms·

I remember this post from 2012 being when "everyone" decided it was enough. https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/ https://eev.ee/blog/201

• develatio 4y ago
  I was expecting to see this link somewhere here in the comments as soon as I saw the title :)
• rzzzt 4y ago
  PHP Sadness #1, "Unexpected T_PAAMAYIM_NEKUDOTAYIM" is still the best error message of all time. http://phpsadness.com/sad/1 http://phpsadness.com/sad/1
  • blowski 4y ago
    If only all error messages were so easily searchable for documentation. I had this error once in 2005. Found the solution quickly. Never had it again.
• ckdot 4y ago
  As a PHP developer for years I like to defend „my“ language. While a few issues he mentioned are true, most of them are outdated or fall into the category „if you do really weird, unusual things you can expect PHP to behave that way, too“. Other languages may prevent such mistakes, but PHP probably doesn’t because it’s historically grown and - like everyone knows - it didn’t start with a totally thought-through architecture. The good thing is, that because PHP has such a long life in web development, you can usually find a lot of docs, libraries and help for probably every problem you’ll habe to solve. If you use PHP in a clean way, you won’t get in touch with most of the quirks he mentioned.