If you really need a lazy Java singleton for some reason, letting the classloader construct it (guaranteed to happen at most once, and as late as possible) is e

If you really need a lazy Java singleton for some reason, letting the classloader construct it (guaranteed to happen at most once, and as late as possible) is effortless and more robust than screwing around with the synchronization yourself. On the other hand, interviewing candidates has so shaken my faith that I'd be very impressed to meet anyone who knew this. http://en.wikipedia.org/wiki/Singleton_pattern#The_solution_of_Bill_Pugh http://en.wikipedia.org/wiki/Singleton_pattern#The_solution_...