<?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>Mon, 20 May 2013 00:14:12 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[The Stubbles Blog: Why we develop Stubbles]]></title>
      <guid>http://www.phpdeveloper.org/news/7491</guid>
      <link>http://www.phpdeveloper.org/news/7491</link>
      <description><![CDATA[<p>
On the Stubbles blog, there's <a href="http://www.stubbles.org/archives/14-Why-we-develop-Stubbles.html">a new post</a> that answers a question they'd mentioned in a <a href="http://www.stubbles.org/archives/4-Pavlov.html">previous post</a> about why they develop the Stubbles framework.
</p>
<blockquote>
<p>
In an <a href="http://www.stubbles.org/archives/4-Pavlov.html">earlier entry</a> I promised that we will explain why we develop Stubbles. Well, there is a short version of it and a long version.
</p>
<p>
Short version: for us.<br/>
Read on for the long version.
</p>
</blockquote>
<p>
He (<i>Franke Kleine</i>) <a href="http://www.stubbles.org/archives/14-Why-we-develop-Stubbles.html">lists out the reasons</a> in his long version, including:
<ul>
<li>Release cycles and maintenance requirements
<li>Why "use your force to improve another framework" is not a valid point
<li>Do we really reinvent the wheel?
<li>More company influence
<li>To open source or to not open source
</ul>
...each with their own justification. Even if some of them are a little weak ("other people started frameworks, why can't we?"), most are good reasons for them to create their own in-house framework that just happens to be released to the rest of the community. Their effort wasn't to create something for the greater good, but to make something that they (and anyone else that might find it useful) could use.
</p>]]></description>
      <pubDate>Fri, 23 Mar 2007 08:29:00 -0500</pubDate>
    </item>
  </channel>
</rss>
