I wish I could downvote a comment that condescending. The Singleton Pattern is, as its name implies, a pattern. It's not a "good pattern", it's not an "anti pa

I wish I could downvote a comment that condescending. The Singleton Pattern is, as its name implies, a pattern. It's not a "good pattern", it's not an "anti pattern",... It is ONLY a pattern whose rightful use relies upon the developper. Is a singleton justified in this case where the developper wants ONE connection object to be used across all his application? I don't see why not. Would a non-singleton object that would be re-instancied upon each file/request/w/ever be better suited? I beg to differ. But if your comment can teach us one thing, it's that for every pattern and every HN comment, the malice resides only between keyboard and chair.