<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Fri, 16 May 2008 00:51:08 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Michael Kimsal's Blog: Why not PHP for Google's App Engine?]]></title>
      <guid>http://www.phpdeveloper.org/news/9950</guid>
      <link>http://www.phpdeveloper.org/news/9950</link>
      <description><![CDATA[<p>
In a recent post to his blog, <i>Michael Kimsal</i> <a href="http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/">asks a question</a> that I'm sure PHP developers everywhere are wondering - why did Google choose to go with Python as the programming language of choice for their new <a href="http://www.techcrunch.com/2008/04/07/google-jumps-head-first-into-web-services-with-google-app-engine/">App Engine</a> service.
</p>
<blockquote>
TechCrunch is announcing Google's new "App Engine" service being launched this evening.  The basic service is a full app stack hosted and managed by Google, providing a web framework (maybe I'm misreading this?) and the Google 'big table' database service. [...] My question is "why was Python was chosen instead of PHP?"
</blockquote>
<p>
There's been some <a href="http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/#comments">great responses</a> since it was originally posted including everything from agreement to rationalizations for the move (though there is a fair amount of PHP and Python bashing going on - an obvious occurance).
</p>]]></description>
      <pubDate>Thu, 10 Apr 2008 12:11:02 -0500</pubDate>
    </item>
  </channel>
</rss>
