title: Are static methods always held in memory?
body: <p>My whole development team thinks, static methods are a terrible thing to use.</p>
  
  <p>I really don't see any disadvantages in some cases. When I needed a stateless method before, I always used static methods for that purpose.</p>
  
  <p>I agree with some of their points, e.g. I know they are quite hard to test (although it's not impossible).</p>
  
  <p>What I don't get is, that they claim, static methods are always held in memory and will fill the basic memory usage. So, if you are using 100 static methods in your program, when the program starts all methods are loaded into memory and will fill the memory unnecessarily. Furthermore static methods increase the risk of memory leaks.</p>
  
  <p>Is that true?</p>
  
  <p>It's quite inconvenient to have to create a new instance of a class just to call the method. But thats how they do it right now, the create a instance in mid of a method and call that method, that could be just a static one.</p>