I second this view. Unless of course one is heavily tied to and 'dependent' on a DI framework.
*On Thu, May 16, 2013 at 6:52 PM, de Witte <wd.dewi...@gmail.com> wrote:* > Aren't you a bit overrating with your subject title? > > Dependency injection a la guice and spring, are frameworks which you want > to avoid as much as possible. > > > Op donderdag 16 mei 2013 01:52:51 UTC+2 schreef Jeff Schnitzer het > volgende: >> >> I attended the "Autoscaling Java" session at Google I/O. In summary, the >> advice is: >> >> * Don't use dependency injection. >> * Don't use AOP. >> * Hardcode configuration values as much as possible. >> >> In other words, go back to Java circa 2002. There was no discussion of >> changing routing so that user requests don't see cold starts. I asked about >> this in person - apparently they're still "talking about it" and nothing >> has been done about it. >> >> I am sad. >> >> Jeff >> > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to google-appengine@googlegroups.com. > Visit this group at http://groups.google.com/group/google-appengine?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
