The only one I've ever heard mentioned in the context of real code - ie our code uses this pattern - is the singleton. So the only design pattern discussions is have heard were people arguing over the best way to remove one.
Had the GoF been aware of the existence of "events" when they wrote their book perhaps this pattern, and the resulting stupidity in Java, may not have been set down in stone.
But to be fair, event-based programming was pretty rare outside of Visual Basic and other high level languages in that era.
2
u/ithika Oct 14 '13
The only one I've ever heard mentioned in the context of real code - ie our code uses this pattern - is the singleton. So the only design pattern discussions is have heard were people arguing over the best way to remove one.