<?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>Fri, 24 May 2013 12:22:16 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Ulrich Kautz: C-based Web Frameworks for PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/19246</guid>
      <link>http://www.phpdeveloper.org/news/19246</link>
      <description><![CDATA[<p>
In <a href="http://foaa.de/blog/2013/02/21/c-based-frameworks-for-php/">this recent post</a> to his site <i>Ulrich Kautz</i> takes a look at an interesting development in the PHP framework world - C-based frameworks installable as PHP extensions. He covers some of the good and bad things about this approach.
</p>
<blockquote>
At the End of 2012 I had my first contact with a C-based PHP frameworks, namely <a href="http://www.yafdev.com/">YAF</a>. Coincidently, some day afterwards <a href="https://twitter.com/bitfalls">Bruno</a> from <a href="http://phpmaster.com/">phpmaster.com</a> pointed me towards <a href="http://phalconphp.com/">Phalcon</a> - a more modern interpretation of the same idea. So I was hooked.
</blockquote>
<p>
In his "good idea" category he notes that it's faster because it's already loaded in on the request (no long list of includes) and the memory footprint is less than a PHP equivalent. The "bad" side of things mentions some pretty major hurdles though, including the small communities vs larger ones on PHP-based frameworks and the issues that could come with debugging/upgrading. 
</p>]]></description>
      <pubDate>Wed, 27 Feb 2013 11:09:46 -0600</pubDate>
    </item>
  </channel>
</rss>
