<?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, 19 Jul 2008 05:48:08 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Stefan Mischook's Blog: PEAR vs. Zend Framework]]></title>
      <guid>http://www.phpdeveloper.org/news/9793</guid>
      <link>http://www.phpdeveloper.org/news/9793</link>
      <description><![CDATA[<p>
On his blog today, <i>Stefan Mischook</i> <a href="http://www.killerphp.com/articles/pear-vs-zend-framework/">compares</a> two of the popular component libraries out there - PEAR and the Zend Framework (yes, it can be considered a grouping of components too).
</p>
<blockquote>
Now that the Zend Framework is ready for 'prime time', I've been considering the <a href="http://pear.php.net/">Pear framework</a> with regards to how it now fits in the PHP world.
</blockquote>
<p>
He <a href="http://www.killerphp.com/articles/pear-vs-zend-framework/">suggests</a> that not could both be considered component libraries, but might also both be frameworks (based on a definition that a framework is a "consistent set of components that are designed to work together in a unified manner"). He also asks about the need for something like PEAR now that the Zend Framework has come along, getting <i>Jonathan Lebensold</i>'s opinion too.
</p>]]></description>
      <pubDate>Fri, 14 Mar 2008 07:56:53 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Lukas Smith's Blog: You can't always get what you want...]]></title>
      <guid>http://www.phpdeveloper.org/news/9679</guid>
      <link>http://www.phpdeveloper.org/news/9679</link>
      <description><![CDATA[<p>
Piggybacking on a <a href="http://news.php.net/php.internals/35562">recent proposal</a> for traits in PHP, <i>Lukas Smith</i> has <a href="http://pooteeweet.org/blog/0/1006#m1006">suggested something</a> that could help make the organization of these sorts of contributions (and their "staying power") a bit more likely to happen - an official PHP.net wiki of sorts.
</p>
<blockquote>
As such I really like what Stefan has done with his <a href="http://www.stefan-marr.de/rfc-traits-for-php.txt">Traits proposal</a>. Very nicely done. [...] Right now the RFC documents are hidden away in the unwieldy mailinglist archive and Stefan's private homepage, which could disappear any day. Of course there are also the various web archives, but what would be nice to have is a PHP.net wiki.
</blockquote>
<p>
He notes that not only would this help protect information like this from dropping off the face of the web but it might also pave the way for some other changes to be made to the language (and to provide a space where everyone can share their ideas). He specifically mentions his wants for an array_merge_replace and a change to file_exists.
</p>]]></description>
      <pubDate>Thu, 21 Feb 2008 11:13:00 -0600</pubDate>
    </item>
  </channel>
</rss>
