<?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>Wed, 19 Jun 2013 15:59:48 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Ibuildings Blog: PHP in 2010 - a year in retrospective]]></title>
      <guid>http://www.phpdeveloper.org/news/15699</guid>
      <link>http://www.phpdeveloper.org/news/15699</link>
      <description><![CDATA[<p>
On the Ibuildings blog today <i>Barney Hanlon</i> <a href="http://www.ibuildings.co.uk/blog/archives/1604-PHP-in-2010-a-year-in-retrospective.html">takes a look at 2010</a> and some of the major happenings in the world of PHP.
</p>
<blockquote>
Every year, for the past three years, Ibuildings has <a href="http://www.ibuildings.co.uk/blog/archives/1583-PHP-in-2009-A-year-in-retrospective.html">written a retrospective</a> of the past twelve months in PHP. Looking back at last year's post, it amazes me how quickly what we were talking about is now passe. Was it only 2009 that Twitter became mainstream? Though not a heavy contributor to the 140-character medium, I find it one of the best ways to keep track of what's going on in the community. Did we only really have the last twelve months to enjoy Google Chrome? It seems to have been my choice of browser for far longer.
</blockquote>
<p>
Some of the events mentioned included the updates that came with PHP 5.3, the end of life on PHP 5.2, the continued involvement of Microsoft in the PHP community and a trend towards more agile development of PHP projects. 
</p>
<blockquote>
With companies looking for further cost reductions and clever new ways of doing things, open source is often a viable option to help meet these goals. Our job, as the community, is to make sure PHP can meet the complex demands of its users. 
</blockquote>]]></description>
      <pubDate>Fri, 07 Jan 2011 08:03:43 -0600</pubDate>
    </item>
  </channel>
</rss>
