<?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>Thu, 04 Dec 2008 13:26:14 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Ian Bicking's Blog: What PHP Deployment Gets Right]]></title>
      <guid>http://www.phpdeveloper.org/news/9410</guid>
      <link>http://www.phpdeveloper.org/news/9410</link>
      <description><![CDATA[<p>
On his blog, <i>Ian Bicking</i> has <a href="http://blog.ianbicking.org/2008/01/12/what-php-deployment-gets-right/">posted some of his thoughts</a> on a positive look at PHP - what he thinks PHP has done right.
</p>
<blockquote>
With the recent talk on the blogosphere about <a href="http://blog.dreamhost.com/2008/01/07/how-ruby-on-rails-could-be-much-better/">deployment</a> (and <a href="http://www.b-list.org/weblog/2008/jan/10/hosts/">for Django</a>, and lots of other posts too), people are thinking about <a href="http://comments.deasil.com/2008/01/11/lessons-to-be-learned-from-php/">PHP</a> a bit more analytically. I think people mostly get it wrong.
</blockquote>
<p>
He <a href="http://blog.ianbicking.org/2008/01/12/what-php-deployment-gets-right/">points out</a> that PHP, in essence, is a CGI-style execution and, in being so, makes it more flexible. Both sides, web and command line, can work with the language equally well. He also mentions the developer/administrator split he sees in PHP's structure and how the language facilitates it.
</p>]]></description>
      <pubDate>Sat, 12 Jan 2008 19:13:09 -0600</pubDate>
    </item>
  </channel>
</rss>
