<?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>Sun, 07 Sep 2008 09:10:13 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[SitePoint PHP Blog: What's so bad about the Singleton?]]></title>
      <guid>http://www.phpdeveloper.org/news/9624</guid>
      <link>http://www.phpdeveloper.org/news/9624</link>
      <description><![CDATA[<p>
On the SitePoint PHP Blog today <i>Troels Knak-Nielsen</i> asks th3e question "what's so bad about the singleton?" For all of its advantages, is there a darker side of the design pattern when it pertains to global variables.
</p>
<blockquote>
As I have often taken this stance myself, I found it reasonable that I should be able to argue for it, so I'll try to give an explanation. This is also in part a follow-up on <a href="http://www.sitepoint.com/blogs/2008/02/04/dealing-with-dependencies/">my post from last week</a>, in which I present a way to avoid global symbols, without spending much time on why.
</blockquote>
<p>
He <a href="http://www.sitepoint.com/blogs/2008/02/13/whats-so-bad-about-the-singleton/">talks about</a> what they are and how they're commonly used - sometimes with some unpleasant side effects because of their use of globals.
</p>]]></description>
      <pubDate>Wed, 13 Feb 2008 12:13:00 -0600</pubDate>
    </item>
  </channel>
</rss>
