|author||Sam Berlin <email@example.com>||Wed Jul 09 20:29:47 2014 -0400|
|committer||Sam Berlin <firstname.lastname@example.org>||Wed Jul 09 20:38:07 2014 -0400|
Wrap GcFinalization usage around wrappers that also await a ReferenceQueue. I couldn't get any failures internally in 10,000 runs even w/o these changes, but on the external builds I reliably reproduced some flakes in 100 runs w/o this, and no flakes (that I saw) afterwards. ------------- Created by MOE: http://code.google.com/p/moe-java MOE_MIGRATED_REVID=70835114
Now, out in 4.0 Beta4!
Put simply, Guice alleviates the need for factories and the use of new in your Java code. Think of Guice's @Inject as the new new. You will still need to write factories in some cases, but your code will not depend directly on them. Your code will be easier to change, unit test and reuse in other contexts.
Guice embraces Java's type safe nature, especially when it comes to features introduced in Java 5 such as generics and annotations. You might think of Guice as filling in missing features for core Java. Ideally, the language itself would provide most of the same features, but until such a language comes along, we have Guice.
Guice helps you design better APIs, and the Guice API itself sets a good example. Guice is not a kitchen sink. We justify each feature with at least three use cases. When in doubt, we leave it out. We build general functionality which enables you to extend Guice rather than adding every feature to the core framework.
Guice aims to make development and debugging easier and faster, not harder and slower. In that vein, Guice steers clear of surprises and magic. You should be able to understand code with or without tools, though tools can make things even easier. When errors do occur, Guice goes the extra mile to generate helpful messages.
We've been running Guice in mission critical applications since 2006, and now you can, too. We hope you enjoy it as much as we do.