There has been a little bit of buzz over the Guice 1.0 announcement.
Guice is a new Dependency Injection framework written specifically for Java 5 and up, and is thus able to think of things in that context. Generics support is first class etc.
Some people have already asked about competition with Spring, which really shows how many people don’t get what Spring is :)
Spring is an enterprise Java productivity framework in my mind. It happens to include a DI framework at the heart of it, but that isn’t all it is.
Guice on the other hand aims to just tackle the DI piece, and comes at it from a different angle.
Rather than seeing the competition I saw the possibilities of using the two together. They already both support the AOP Alliance APIs so you can play nicely. You can choose to use Guice DI with Spring helpers.
So, before we get into a “Spring vs. Guice” mindset, let’s remember how incredibly different they are.
You can read about a comparison from the Guice point of view.
And then Joe goes and writes A Spring competitor from Google :)
March 9th, 2007 at 1:56 pm
Big deal, like who HASN’T written an IoC container. Or two. Seriously, Guice has a couple of cool ideas, but I sincerely believe its goals (and a lot of other ones besides) are better met with Tapestry 5 IoC, which goes a lot further in terms of convention over configuration (via naming conventions and occasional annotations).
Tapestry 5 IoC also supports distributed configuration (much like HiveMind), which is key to plugin support with zero configuration.
June 1st, 2007 at 7:02 pm
Guice looks like a very elegant piece of code. For that alone I like it a lot.
October 7th, 2007 at 6:59 am
porn
October 7th, 2007 at 7:00 am
porn
January 24th, 2008 at 10:11 pm
[...]to think of things in that context. Generics support is first class etc.[...]
May 19th, 2008 at 12:25 am
thanks for sharing,generous blogger
June 23rd, 2008 at 4:37 am
thank you!
May 27th, 2009 at 6:22 pm
we get into a “Spring vs. Guice” mindset, let’s remember how incredibly different they are.