Comments on: The much dreaded Singleton http://blog.controul.com/2009/02/the-much-dreaded-singleton/ Elaborations on flash. Tue, 27 Jul 2010 09:31:06 -0700 hourly 1 http://wordpress.org/?v=3.0 By: Alan Shaw http://blog.controul.com/2009/02/the-much-dreaded-singleton/comment-page-1/#comment-63 Alan Shaw Fri, 22 May 2009 03:28:26 +0000 http://blog.controul.com/?p=25#comment-63 I too have been a fan of Hevery for a while. I was looking forward to gaining deeper understanding of his concepts as I implemented true unit testing and moved toward continuous integration in a Flex project... and the project was abruptly cancelled. All interesting stuff, but left to my own devices I tend to get more into geometric programming. I too have been a fan of Hevery for a while. I was looking forward to gaining deeper understanding of his concepts as I implemented true unit testing and moved toward continuous integration in a Flex project… and the project was abruptly cancelled. All interesting stuff, but left to my own devices I tend to get more into geometric programming.

]]> By: hristo http://blog.controul.com/2009/02/the-much-dreaded-singleton/comment-page-1/#comment-11 hristo Thu, 09 Apr 2009 19:12:19 +0000 http://blog.controul.com/?p=25#comment-11 I'll post about this, results are insanely divergent among players. EDIT: <a href="http://blog.controul.com/2009/04/how-slow-is-static-access-in-as3avm2-exactly/" rel="nofollow">Done</a>. I’ll post about this, results are insanely divergent among players.
EDIT: Done.

]]> By: dVyper http://blog.controul.com/2009/02/the-much-dreaded-singleton/comment-page-1/#comment-10 dVyper Thu, 09 Apr 2009 10:05:00 +0000 http://blog.controul.com/?p=25#comment-10 I'm interested in this - what proof is there that accessing static variables is 10 times slower to access? I’m interested in this – what proof is there that accessing static variables is 10 times slower to access?

]]> By: hristo http://blog.controul.com/2009/02/the-much-dreaded-singleton/comment-page-1/#comment-3 hristo Fri, 27 Feb 2009 15:01:28 +0000 http://blog.controul.com/?p=25#comment-3 Hey Bill, Miško Hevery’s series of posts on Singletons are indeed a great read, which I have come across before, I believe, from links on your blog. I will soon come back to this topic with a practical example that we can discuss throughout. Thank you for the reply! Hey Bill,

Miško Hevery’s series of posts on Singletons are indeed a great read, which I have come across before, I believe, from links on your blog.
I will soon come back to this topic with a practical example that we can discuss throughout. Thank you for the reply!

]]> By: Bill Sanders http://blog.controul.com/2009/02/the-much-dreaded-singleton/comment-page-1/#comment-2 Bill Sanders Fri, 27 Feb 2009 10:38:51 +0000 http://blog.controul.com/?p=25#comment-2 Hi Hristo, I like your post on Singletons even though I've quit using them, and I don't believe that they've suffered the martyrdom you suggest.(They deserve to be kicked around a lot more!) The fact that you have thought about them and their advantages and limitations puts you way beyond most developers. Miško Hevery's post <a href="http://misko.hevery.com/2008/08/17/singletons-are-pathological-liars/" rel="nofollow">Singletons are Pathological Liars</a> is one of the best explanations of why to avoid Singletons—they act like global variables and break encapsulation. Of course people love and use Singletons, and that is the very reason they're so dangerous. It's almost like placing a virus in your own code. One alternative to Singletons is simply to use the Client as your entry point. Many design patterns include the placement of the Client module in the class diagram (implied or as an integral part of the pattern) along with the kind of reference to the different modules. Some references are to a single module and others, like the Abstract Factory, are multiple and complex. However, what they all have in common is that they maintain the integrity of the components and keep the design open for re-use and update. Let's keep this discussion going. Kindest regards, Bill Hi Hristo,

I like your post on Singletons even though I’ve quit using them, and I don’t believe that they’ve suffered the martyrdom you suggest.(They deserve to be kicked around a lot more!) The fact that you have thought about them and their advantages and limitations puts you way beyond most developers.

Miško Hevery’s post Singletons are Pathological Liars is one of the best explanations of why to avoid Singletons—they act like global variables and break encapsulation. Of course people love and use Singletons, and that is the very reason they’re so dangerous. It’s almost like placing a virus in your own code.

One alternative to Singletons is simply to use the Client as your entry point. Many design patterns include the placement of the Client module in the class diagram (implied or as an integral part of the pattern) along with the kind of reference to the different modules. Some references are to a single module and others, like the Abstract Factory, are multiple and complex. However, what they all have in common is that they maintain the integrity of the components and keep the design open for re-use and update.

Let’s keep this discussion going.

Kindest regards,
Bill

]]>