<?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>Sat, 18 May 2013 11:37:35 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Henri Bergius' Blog: PHP: Finally getting an ecosystem?]]></title>
      <guid>http://www.phpdeveloper.org/news/15483</guid>
      <link>http://www.phpdeveloper.org/news/15483</link>
      <description><![CDATA[<p>
In <a href="http://bergie.iki.fi/blog/php-finally_getting_an_ecosystem/">this new post</a> to his blog <i>Henri Bergius</i> takes a step back and wonders if PHP is finally getting an ecosystem of its own (and not leaning of those of PHP-based projects.
</p>
<blockquote>
One of my main concerns with PHP has been the lack of ecosystem. Almost all libraries and tools are written with a specific framework in mind, creating separate ecosystems around <a href="http://drupal.org/project/modules">Drupal</a>, <a href="http://framework.zend.com/apidoc/1.11/">Zend Framework</a>, <a href="http://trac.midgard-project.org/browser/branches/ragnaroek/midcom">Midgard</a> and others instead of an ecosystem benefiting all users of the language. There have been efforts at this, like PEAR before, but they have mostly stagnated.
</blockquote>
<p>
These thoughts were spurred on by <a href="http://schlitt.info/opensource/blog/0737_apache_zeta_components_was_ez_components.html">a post</a> about the changes happening with <a href="http://ezcomponents.org/">eZ components</a> (into <a href="http://incubator.apache.org/zetacomponents/">Zeta Components</a>) and how they can help reinforce the strength of the language rather than the efforts of one specific project's ecosystem.
</p>]]></description>
      <pubDate>Wed, 24 Nov 2010 09:56:04 -0600</pubDate>
    </item>
  </channel>
</rss>
