The recommendation to use Dagger seems to have some merit and it would seem to make some sense that Google would push towards Dagger, given its suitability for Android. I use GAE/J as a backend to Android (and based on io13 sessions, Google is rather pushing this) so things that work well on both GAE/J and Android are attractive.
On a general note, at the end of the keynote someone asked a question suggesting that Google's dependency on a language they don't control was a big problem. I hope that is not the reason behind the lack of progress on GAE/J. I realize that is a common mentality but it is a sad state of affairs and it seemed to me to go against the thrust of Page's speech. Tom On Friday, May 17, 2013 10:35:31 AM UTC-4, Vinny P wrote: > > +1 to Jeff and this thread. > > I was at the same I/O session, and I received the same impression of > Java/GAE as Jeff. The recommendation against DI/AOP is a big issue, > considering how many Java frameworks and abstractions depend upon those. > > ----------------- > -Vinny P > Technology & Media Advisor > Chicago, IL > > My Go side project: http://invalidmail.com/ > > On Thursday, May 16, 2013 11:14:20 AM UTC-5, Jeff Schnitzer wrote: >> >> No, I'm not "overrating" with my subject. >> >> The apparent reasoning behind those points is that Google still thinks >> "startup time is your problem", and routes user requests to cold starts. >> This works in Go but it will never work in Java. The last time I made a >> Hello, World app with JPA it took 4-5 seconds to startup in production. >> Somewhere around 5 seconds is where the user thinks your app is broken and >> hits the reload button. If Google Search pages took 5 seconds to load for >> a significant percentage of users, heads would roll. >> >> If your app actually _does something_ it's going to take more than 5s to >> load. Maybe you can make it 10s instead of 30s by adopting 2000s-era >> programming practices, but it doesn't matter because the user has already >> considered your app broken. >> >> And don't get me started on the frequent "sick periods" where startup >> time goes up by 3X... >> >> Jeff >> >> >> >> On Thu, May 16, 2013 at 9:22 AM, de Witte <wd.de...@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.
