Eric discovered that Guice really does result in less code:
At the end of the day, I compared my [Guice] modules — written in Java — to my Spring XML files. The modules are significantly smaller and easier to read. Then I realized about 3/4 of the code in my modules was unnecessary, so I stripped it out. They were reduced to just a few lines of code each.
Eric noticed another feature which you can't really appreciate until you actually use Guice:
The error messages are exceptionally good when things go wrong. You can tell they put a lot of effort into this, and this is HUGE. Every single framework should learn this lesson: cryptic error messages are a major drain on developer productivity, and we really appreciate tools like Guice.
We invested countless hours into making Guice's error messages as helpful as possible. We use plain English. We print line numbers (in such a way that IDEs automatically link to source code). We suggest likely causes and even fixes.
In the end, it sounds like Eric is sold:
I successfully converted the client, but ran out of time for the server piece. Based on what I did accomplish, however, I definitely plan to finish the job as soon as possible.
We'll look forward to the rest.
Disclosure: I used to consult for OCI, too, but didn't work with Eric. Many consulting firms abuse their brand to trick clients into paying top dollar for off-the-street programmers with no real qualifications. If you're looking for a consulting/training firm with real top talent, I highly recommend OCI. I'm not just saying that because Eric wrote a favorable review either. :)