How is that a language-level feature? Unless the comparison is to framework level features like ASP.NET Session State, but PHP would only work around that by using memcached or something, right? Or is this referring to the fact that I can't have shared variables at all, so I can't cache super common data structures in a local piece of RAM?
"2. I won’t need experts" - It must be nice, if boring, to be working on really simple codebases where anyone that can hack PHP can work on your application.
"10. Dynamic typing" - There are plenty of neat reasons for dynamic typing, like easy metaprogramming and whatnot. Having crazy type coercion isn't one of them. And "HTTP is untyped so should PHP"; I'm not sure what to make of this.
This goes along with "11. It plain works" -- yea, depends on how you define works. "A lot of that is based on “assumptions” (or shortcuts) that PHP takes to solve a problem. Most often those shortcuts work, and the workarounds are very easy to implement (I’m thinking mainly about strict type checking here)."
And that's the real issue that I can see with PHP. Sometimes, some stuff might sorta make sense, and the rest of the time you're in this weird "gotcha" land, with the inconsistent API and language design.
The only compelling reason I've seen for using PHP is "well, pretty much every server has it installed, and it's super easy to get working with a webserver". PHP seems to surpass everything else in that particular area. Apart from that, come on...