<?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, 21 May 2012 09:35:28 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Matt Curry's Blog: .8 Reasons to hate CakePHP]]></title>
      <guid>http://www.phpdeveloper.org/news/11642</guid>
      <link>http://www.phpdeveloper.org/news/11642</link>
      <description><![CDATA[<p>
In response to <a href="http://ajbrown.org/blog/2008/12/22/four-reasons-to-hate-cakephp/">this recent post</a> on four reasons to hate CakePHP, <i>Matt Curry</i> has <a href="http://www.pseudocoder.com/archives/2008/12/23/8-reasons-to-hate-cakephp/">posted some of his thoughts</a> over on his pseudocoder.com blog to refute the comments made.
</p>
<blockquote>
I'm still bored and lacking posting ideas, so I figured I'd give a hyper-critical breakdown of "<a href="http://ajbrown.org/blog/2008/12/22/four-reasons-to-hate-cakephp/">Four reasons to hate CakePHP</a>" by A.J. Brown. Let's get right into it.
</blockquote>
<p>
He responds to comments on: CakePHP's "heaviness", the (in)flexibility the framework allows, alpha releases, changes between versions, no namespace considerations and its use of global functions.
</p>
<p>
You can see the original post here: <a href="http://ajbrown.org/blog/2008/12/22/four-reasons-to-hate-cakephp.html">Four reasons to hate CakePHP</a> as well as his AJ's own response to comments he recieved - <a href="http://ajbrown.org/blog/2008/12/23/maybe-i-was-too-hard-on-cakephp.html">Maybe I was too hard on CakePHP</a>.
</p>]]></description>
      <pubDate>Tue, 30 Dec 2008 12:06:54 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Mike Bernat's Blog: PHP Cookies vs Sessions - The Breakdown]]></title>
      <guid>http://www.phpdeveloper.org/news/6902</guid>
      <link>http://www.phpdeveloper.org/news/6902</link>
      <description><![CDATA[<p>
In a <a href="http://www.mikebernat.com/mikebernat.com/new/?a=article&id=PHP%20Cookies%20vs%20Sessions%20-%20The%20Breakdown">recent post</a> to his blog, <i>Mike Bernat</i> gets down to basics with one of the key pieces of functionality in PHP data persistence - cookies vs. sessions.
</p>
<blockquote>
Knowing the basics of cookies and sessions is essential to any successful PHP programmer. It is useful to store pieces information on the users computer for later use. Things like when they last visited, language of choice, age, etc. Cookies and Sessions are the perfect solution to our needs.
</blockquote>
<p>
He <a href="http://www.mikebernat.com/mikebernat.com/new/?a=article&id=PHP%20Cookies%20vs%20Sessions%20-%20The%20Breakdown">talks about both</a>, including demonstration code to clarify some points and a chart at the end to compare their features, strengths, and weaknesses.
</p>]]></description>
      <pubDate>Thu, 14 Dec 2006 16:58:00 -0600</pubDate>
    </item>
  </channel>
</rss>

