title: Play! framework uses a <lot> of statics
body: <p>Waaah, the Play! framework has so many static methods. Where I go to school, we were told <em>never ever</em> to use any statics, yet Play! uses it like there's no tomorrow. Is that somehow okay? If so, why?</p>
  
  <p>We (7 people and I) are planning to use the Play! framework for a project involving a web app. We decided to do it with Play! because it looks quite fun to do, all of us already know Java and the assignment is pretty hard so we wanted to focus on the actual assignment rather than also learning how to program in a different language.</p>
  
  <p>We were always told, however, <em>NEVER EVER</em> to use 'static's in any Java program we developed, but when I look at Play! ... Well... about half the methods are static. &lt;/exaggeration&gt;</p>
  
  <p>I suppose, at the very least, we could use singleton objects (by using Scala, for example ^^) in order to program our project, but I'm quite concerned at how many statics there actually are in framework itself.</p>
  
  <p>So, should I be concerned about this? Did the way the Play! developers programmed it make it so that all these statics don't pose a problem?</p>
  
  <p>(For example, <a href="http://www.allegro.cc/forums/thread/586752" rel="noreferrer" title="this thread">this thread</a> has a rant about why static members should be avoided at all costs.)</p>