How Bad Are Singletons?

Question

So ....

There are obviously many questions that all have been asked about Singletons, Global State Variables, and all that great stuff. My question is,

If Singletons and Globals are So Bad, Why are they used so often?

The following examples are simply ones off the top of my head that I believe are used by a good chunk of people.

I give you a function from CodeIgniter that uses a psuedo-singleton function:

(system\codeigniter\Common.php Line 89)

/**
* Class registry
*
* This function acts as a singleton.  If the requested class does not
* exist it is instantiated and set to a static variable.  If it has
* previously been instantiated the variable is returned.
*
* ......
*/
function &load_class($class, $instantiate = TRUE)
{
    static $objects = array();

    // Does the class exist?  If so, we're done...
    if (isset($objects[$class]))
    {
        return $objects[$class];
    }
  .......
}

By placing every object into a single registry, you can't use their load_class function to create multiple instances of anything. This is especially inconvenient when you want to use classes as data structures.

Also, because there is only one instance of all those classes, it leads into the argument against Global State. Which leads me to .....

The entire Wordpress System, which runs mainly on global variables. All of the data for looping through posts is strewn about in various globals.

(wp-includes\query.php Line 2644)

/**
 * Setup global post data.
 *
 *....
 */
function setup_postdata($post) {
    global $id, $authordata, $day, $currentmonth, $page, $pages, $multipage, $more, $numpages;

    $id = (int) $post->ID;

    $authordata = get_userdata($post->post_author);
    ....
}

These are just two main examples of Frameworks that use Singleton/Globals as the basis for their entire system!

So .. is it just because these systems haven't caught up to OOP methodology? It just doesn't make sense when you have so many people telling you not to use Global Variables or Singletons, to make your entire system based on said practices.

There of course is the argument about backwards-compatibility with PHP4. I still think that there were ways to do OOP programming in PHP4, as classes were still available.

Answer 1

Reasons in PHP4-based apps like WP or CI are partially due to PHP4's worse support of OOP constructs.

Globals and singletons are also simple: It requires much less thinking to slap something in a global than building it with proper OOP practices. It's simpler to access them too, just point the code at the name and that's it instead of needing to pass the object in from somewhere else.

One negative side effect of global state (global variables, singletons, etc.) is that it makes things much more difficult to unit test.

ps: In my experience wordpress in general has a pretty poor quality of code. I would not use it as a metric of anything...