Why Google App Engine Shouldn't Include PHP
He seems to be saying "PHP shouldn't be supported because its a bit of an ugly language and somewhat insecure"
But then should they only support Scheme? :]
The problem is theres so much useful {badly written} PHP code out there, its going to be hard to ignore.
I guess they'll _have_ to adopt PHP, Python, Ruby/Rails in order to get user volume.
Which language is better is probably irrelevant.
While the comment that many PHP applications depend on a MySQL database (I'd seriously expect WP to have some sort of DAL by now) is true it wouldn't be impossible for someone to write an extension to support Google's BigTable.
Article was a little confusing(ly structured) but surprised me by not completely bashing PHP.
I haven't actually used GAE and assume BigTable is another database platform.
It may already be too late, PHP on the JVM:
http://www.caucho.com/resin-3.0/quercus/
Note, I know nothing about the project, just first result from Google. I knew something existed because I'd read about IBM's Project Zero, but I think their implementation of PHP on the JVM (called P8, iirc) is closed source.
Has blatant PHP bashing been made so taboo around here that we must now endure passive-aggressive PHP bashing?
Wow, this is a horrible article. Where does the author get his facts about the quality level of "most" PHP developers? Sounds like typical religious flaming and half-arsed fud.
The argument being made is unclear. Is the author saying that Google App Engine should not support PHP because PHP is not a robust language? If so, that's not a very persuasive argument.
More importantly, this is a very poor piece of writing, the worst I've seen in some time. For starters, the author would do well to learn how to write a thesis statement: