Link Details

The motive is good :)

finally a post talks about what should be talked about regarding singlton

Wasn't one of the "features" of the singleton design pattern that you can replace:
public static MyBigObject getInstance() {
return INSTANCE;
}
with:
public static MyBigObject getInstance() {
return new MyBigObject();
}
to change away from the singleton (without changing any other code).
I guess that's really the factory pattern part of a singleton.
Maybe the anti-singleton rhetoric is really pro-factory
;-)

I dont know about other people but I used (and saw it as a feature of singletons) == for equality on singletons quite a lot for some time. So if some people are like me, which I am quite sure there are, then it wont be just that easy. Maybe this is one of the reasons its considered an antipattern..

So naive, the bloke has no real clue why Singletons exist or how to use them properly, his 'solution' looks a lot worse than a Singleton, especially for multi-threaded code.

willcode4beer:
No factories are not the same as Singletons. Factories can have an interface and different implementations or instances. and only provide objects which are instances of a class or interface. Singletons have at most one instance per context and can receive or return primitive or object values, they can act like factories, but not all factories are Singletons..

Enum objects are Singletons too!