A few reasons why PHP Sucks!!!!!!!!!!

[mandy]

2 articles pointing out a few problems with PHP:

Here’s what makes PHP a toy and not a tool. I can’t stress that enough. If you’re planning to develop a software system and you have a choice on which technology you want to implement it: there is almost NO reason for implementing it with PHP, but a lot of reasons against. I already used PHP when it was called PHP/FI. I understand that today’s PHP has organically grown out of that CGI binary. But unfortunately PHP is now being marketed as a “enterprise-class” technology.

  1. There are 3 incompatible versions of PHP.

      There have been 2 forward-incompatible changes in the codebase that make a certain amount of code backward and forward-unportable. While backward-portability is most often not supported, as new versions of the runtime introduce new features, forward-portability, that means backwards-compatibility for the runtime, is a must. Especially for software systems that need big investments to develop...

full article: http://maurus.net/work/php-sucks/

...all the PHP code I’ve seen in that experience has been messy, unmaintainable crap. Spaghetti SQL wrapped in spaghetti PHP wrapped in spaghetti HTML, replicated in slightly-varying form in dozens of places. Everyone agrees on PHP’s upsides: it’s written for the web, it’s easy to deploy and get running, and it’s pretty fast. Those are important advantages. And I’m sure that it’s possible to write clean, comprehensible, maintainable, PHP; only apparently it’s real easy not to. But PHP has competition, most obviously Rails; and don’t write the Java EE crowd off, they’re not stupid at all and they’re trying to learn the lessons that PHP is trying to teach...

full article: http://www.tbray.org/ongoing/When/200x/2006/02/17/PHP

[rose]

..all the PHP code I’ve seen in that experience has been messy, unmaintainable crap. Spaghetti SQL wrapped in spaghetti PHP wrapped in spaghetti HTML, replicated in slightly-varying form in dozens of places.

Sucky programmers used to gravitate to Perl until PHP arrived and made it even easier for beginners to program badly.

[mandy]

Another pair of related articles on why PHP and MySQL suck!!!!! 

Open source software has fought a long battle to get where it is today, and at least 3/4 of the so-called LAMP (Linux, Apache, MySQL, PHP) stack are under vigorous attack by many, myself included. Why?...

I'm quite opposed to using MySQL and PHP, and I'm none too fond of Apache... To be fair, Apache is the least problematic of the three and if there were no alternatives, I'd use it without a lot of complaint.

MySQL and PHP, on the other hand, really raise my ire. Both of them have two major problems:

  1. Bug ridden (by this I am including both misfeatures as well as actual bugs).
  2. They encourage bad habits.

full article: http://blog.develix.com/frog/user/cliff/...06-06-04/9

Whether the designers of PHP intended it to be or not, PHP is widely considered to be a good beginner's language, probably due to its low barrier to entry. Whether they wanted it or not, that's what they've got and this fact must be recognized and accounted for.

Let's go over the various settings in php.ini that can open serious security holes:

  1. register_globals - this injects user-supplied data into the global namespace
  2. allow_url_fopen - allows remote URLs to be opened as if they are local files
  3. magic_quotes_gpc - pretends to protect you from malicious input

full article: http://blog.develix.com/frog/user/cliff/...06-06-06/1

[misteroriginal]

I know the bears take PHP to bed everynight, so I was going to shock them with a "Why PHP Sucks Eggs" post. Unfortunately, the robotic Mandy is half a year ahead of me once again. Dammit!

OK, let me just add a link that shows the beginning of the overdue PHP decline:
http://www.php.net/usage.php