<?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 14:02:32 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Phil Sturgeon's Blog: Packages: The Way Forward for PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/17636</guid>
      <link>http://www.phpdeveloper.org/news/17636</link>
      <description><![CDATA[<p>
In <a herf="http://philsturgeon.co.uk/blog/2012/03/packages-the-way-forward-for-php">this new post</a> to his blog <i>Phil Sturgeon</i> talks about what he (and apparently several others) think is the "way forward for PHP" to make it a better language and ecosystem - packages.
</p>
<blockquote>
What is a package? A package is a piece of reusable code that can be dropped into any application and be used without any tinkering to add functionality to that code. [...] Most package systems also allow for something called dependencies. [...] This is how most modern programming languages work, but to make a generalisation: PHP developers hate packages. Why? Well while other languages have great systems like <a href="http://www.cpan.org/">CPAN</a> for Perl, <a href="http://rubygems.org/">Gems</a> for Ruby, PIP, PHP has had a terrible history with package management going back years.
</blockquote>
<p>
He talks about one of the main current packaging systems, <a href="http://pear.php.net">PEAR</a>, and how, despite its attempts, it just hasn't seen the adoption the package management of other languages has. <i>Phil</i> makes a recommendation that is slowly becoming more and more popular in the PHP community - building "unframeworks". These sets of reusable components (similar to the ideas behind <a href="http://auraphp.github.com/">Aura</a>, <a href="http://symfony.com">Symfony</a> and <a href="http://framework.zend.com/zf2">Zend Framework 2</a>) are designed to be dropped in and used without the dependencies of the frameworks they live in. He points to the <a href="http://getcomposer.org/">Composer</a>/<a href="http://packagist.org/">Packagist</a> dynamic duo as a way through all of the current packaging issues - a simple way to make any project an installable package just by adding a configuration file.
</p>]]></description>
      <pubDate>Wed, 07 Mar 2012 08:29:57 -0600</pubDate>
    </item>
  </channel>
</rss>
