1. PHP is very flexible. If you don’t want to mix up all your code (as you shouldn’t), and you don’t want to use one of the myriad of framework options out there, it’s incredibly easy to separate your data logic, controller, and view. Hell, you can practically do it with just file includes. Want to keep your data functions separate? Put your data functions in separate files, and include as needed. Want a front controller instead of having the user hit separate files? Send everything through index.php, and use the $_GET data to load whatever controller you’d like. And for your view? Well, PHP is practically a templating language in itself, so just don’t put non-view logic in your view includes!

2. The crap function naming would actually be a pain in the ass if the manual wasn’t so damn useful. It’s 1 part manual, 1 part cookbook. At least half the time I go looking for a php function to solve a simple problem, someone in the comments has already provided me with something I can use. I can’t say this about any other language.

All in all, I know and like ruby, and I know and like python. I also know that I don’t like C# and Java because they aren’t fun to program in for me, although I do appreciate the niche they fill. But I still choose PHP for web projects, because despite the well thought out and articulated lists of flaws provided, it’s got a ton of perks, it’s very flexible, and it does it’s job admirably.

@florin
I don’t understand what you mean by code attached to the “tag id”. Are you talking about having code represented as tags in your view? PRADO (www.xisc.com) does that, and it’s been around since PHP 5.

These statements are utter gibberish – obviously – for one simple reason. There is no context. There is no “when” or “as long as” or “wherever” clause to follow, qualifying when, why, or how, these tools compare to one another.

I see arguments where PHP is a poor (read: horrible) choice for recursion. You know something, I’d have to agree with that. My question becomes… why would you use PHP for recursion? I’ve gotten into a slew of complex algorithms lately, in game design, web crawling, even just automated filesystem maintenance. All with recursive problems. All solved iteratively. To put it simply, given enough time and storage, yes, recursion is one of the most graceful strategies for computation in a dev’s belt. But we, collectively, never have enough time or storage. So, we come up with iterative algorithms. My question, better stated: Why would you use ANY language for recursion? I’ve never yet seen a recursive algorithm that couldn’t be done iteratively.

And, on top of that pile, what language IS good with recursion? Oh sure, some languages may make it seem nice and handy, but under the hood, it’s doing the same things. Pushing and popping mind-boggling numbers of activation records on the runtime stack, quickly ballooning. Go ahead and try running the classic recursive fibonacci function (recursively) on your best PC. Do… say… fib( 100 ). Bet it takes longer than you’d think. Any language you pick.

I picked on the “PHP is poor for recursion” argument off of that initial list of 11 because it was the easiest to make my point, which is this: You wouldn’t use a roll of duct tape as a hammer, and you wouldn’t use a keyboard as a screwdriver. You can take any language, and come up with an infinite number of situations where that language is a poor choice. We can all do that. The trick, the real trick where the “goodness” of a language, and the skill of a programmer comes into play, is that said programmer knows what tool (language) to use for what job, and do so well. You can’t solve every problem with a hammer, and you shouldn’t try to, or else I’d recommend finding a good attorney.

And of course points (1) to (3) also explain why PHP is a poor programming language(*) and prone to security problems – it does magic things, it encourages you to ignore errors, and it discourages separation of concerns.

I’ve heard Guido referred to as many things but “best software architect” hasn’t been one of them.

And about Jeff Atwood, what do you expect from an ASP developer? ASP was the biggest joke in the history of programming languages.

That’s a cheap shot. I would almost call it guilt by association but it isn’t even that good. Its more like guilt by the poster being an idiot.

- Ruby? No one uses it any more. There are better alternatives, like JRuby.
- Python? Sys admin love it. Hey, it’s much better than shell scripting right?
- PHP? Programmers use it, web developers use it, web designer use it, my mom uses it and even my dog uses it. Why use something else?

Python and Ruby cannot and will never compete with languages like Java and/or C, so stop dreaming about it. They might be able to comete against PHP, it’s the only popular scripting language and has its flwas. But, to compete you need to offer something new or solve a problem that hasn’t already been solved.

The biggest issue with Ruby is that its popularity is fading away and they now have a very small and angry community. The issue with Python is that Linux is supporting it, and therefore sys admins are supporting it. And of course, Google supports it, an because of that, lot of fanboys are supporting it as well. The same fanoboys that go from blog to blog writing rants about Java, C, PHP and Ruby.

For me, Ruby is like Delphi, and PHP like Visual Basic. And you know what, although Delphi is far much superior than VB, no one uses it anymore. And you know why? Because it didn’t bring anything new to the table.

Does Python bring something new? No, it’s just another scripting language. But it’s fast, stable, has a great execution model and Google pays one of the best software architects, Guido, to maintain it and improve it.

And about Jeff Atwood, what do you expect from an ASP developer? ASP was the biggest joke in the history of programming languages.

Meanwhile I’ll keep on making good software easily and quickly, and getting paid well to do it while he waits for ‘the next big thing’.

PHP was a success despite being a crap language.

Personally I refuse to use it since several years.

Ruby has replaced it. I can still understand people who use PHP,
but this does not change the fact that PHP as a language is simply horrible,
and I am glad that I no longer need to use it.

The only thing that makes me sad is that the other languages did not yet dethrone PHP, which shows that dethroning another language is not an easy task.

If 10000000000000 flies eat shit, that doesnt mean that shit tastes any good.

As a web developer it pains me to see Internet Explorer to be the #1 browser in planet. But then again, I have to support that crappy thing for the sake of browser compatibility. Why you guys are so pissed off for?

PHP is and will be one of the most popular languages in the web arena.

Accept the fact and suck it up.