IMHO;
Singletons serve a purpose just like every other design pattern.
Having developed/architected quite large frameworks in my day,
Singletons are evil in the context of a framework. You will soon see
when you start unit testing how evil they are. (IE I put one in
FalconJx temporarily to stop jsdocs from being emitted in the unit
tests, now that damn thing is all over the tests and I have to kill it)
As far as applications, I believe it's really up to the developer
because they program what they were taught and familiar with.
Mike
Quoting Harbs <harbs.li...@gmail.com>:
Over the years I'm heard this from time to time, but I never
understood the prejudice. I personally like singletons because it
keeps things nice and simple. I don't like over-engineering things
for no reason.
Care to explain what's wrong with singletons?
On Jan 16, 2013, at 8:41 AM, Avi Kessner wrote:
I'm in the 'singletons are evil' camp.
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
