title: Google Guice vs. PicoContainer for Dependency Injection
body: <p>My team is researching dependency injection frameworks and is trying to decide between using Google-Guice and PicoContainer.</p>
  
  <p>We are looking for several things in our framework:</p>
  
  <ol>
  <li>A small code footprint - What I mean by a small code footprint is we don't want to have dependency injection code litter everywhere in our code base.  If we need to refactor down the road, we want it to be as easy as possible.  </li>
  <li>Performance - How much overhead does each framework have when creating and injecting objects?</li>
  <li>Ease of use - Is there a large learning curve?  Do we have to write mounds of code to get something simple working?  We want to have as little configuration as possible.  </li>
  <li>Community size - Larger communities usually means that a project will continue to be maintained.  We don't want to use a framework and have to fix our own bugs ;)  Also any questions we have along the way can (hopefully) be answered by the framework's developer/user community .</li>
  </ol>
  
  <p>Comparisons of the two frameworks against the listed criteria would be greatly appreciated.  Any personal experiences that help to compare the two would also be extremely helpful.</p>
  
  <p>Disclaimer: I'm fairly new to dependency injection so excuse my noob-ness if I asked a question that isn't pertinent to this discussion. </p>