Comments on: Static method abuse http://jagregory.com/writings/static-method-abuse/ Monkeying with the code Thu, 04 Aug 2011 15:17:48 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Oliver http://jagregory.com/writings/static-method-abuse/comment-page-1/#comment-52284 Oliver Sat, 29 May 2010 11:01:50 +0000 http://blog.jagregory.com/2008/03/28/static-method-abuse/#comment-52284 Excellent argument! These are the kinds of explanations that help people learn. Myself very much included. Static methods are far too easy to misunderstand. Excellent argument! These are the kinds of explanations that help people learn. Myself very much included. Static methods are far too easy to misunderstand.

]]> By: MoffDub http://jagregory.com/writings/static-method-abuse/comment-page-1/#comment-9272 MoffDub Tue, 12 Aug 2008 13:06:24 +0000 http://blog.jagregory.com/2008/03/28/static-method-abuse/#comment-9272 Bravo. I started thinking about singletons vs. static methods today. Over and over I came back to the conclusion that they unnecessarily restrict you in terms of inheritance, polymorphism, interfaces, and potential multi-threading. In order to use either, you'd need a fairly certain idea about the future of the code you are writing -- either that it will be completely stateless, or not used in multi-threading, or its implementation won't vary or need to be injected at some point. And we know that in software engineering, this is probably never the case. I also took a cue from SmallTalk; you'd never see static methods in SmallTalk (to the best of my limited knowledge of SmallTalk). After all, these languages are OO, not CO (class-oriented). ________ The views expressed here are mine and do not reflect the official opinion of my employer or the organization through which the Internet was accessed. Bravo. I started thinking about singletons vs. static methods today. Over and over I came back to the conclusion that they unnecessarily restrict you in terms of inheritance, polymorphism, interfaces, and potential multi-threading.

In order to use either, you’d need a fairly certain idea about the future of the code you are writing — either that it will be completely stateless, or not used in multi-threading, or its implementation won’t vary or need to be injected at some point. And we know that in software engineering, this is probably never the case.

I also took a cue from SmallTalk; you’d never see static methods in SmallTalk (to the best of my limited knowledge of SmallTalk). After all, these languages are OO, not CO (class-oriented).

________
The views expressed here are mine and do not reflect the official opinion of my employer or the organization through which the Internet was accessed.

]]>