Can you recommend what features of Guice you find you want that Dagger does
not offer, and how these relate?  The Dagger and Guice folks are in pretty
regular discussion and are related projects, and it would be nice to know
what we're missing.  Absolutely Guice is more powerful and flexible across
many dimensions - a deliberate decision to constrain APIs in order to
encourage certain patterns, especially in Dagger 2.

Google has some experience (with some good results) simulating the guice
API in a compile-time annotation processor, though it still ended up being
a sub-set of the GUICE total capability.  I'm interested to hear of your
experiences. I will say, I'm really glad people are experimenting with
different approaches.

Also, I should point out that we do have a validation annotation processor
for Guice that we need to roll-out to help with earlier error validation,
though that doesn't address performance constraints.  It's been sitting for
a bit, owing to prioritization, but I think that we should get it in shape
and into Guice soon. (cc:ing colin about that)

Christian.

On Tue Oct 21 2014 at 2:18:15 PM Michael Burton <m...@niskala.org> wrote:

> We are aware of Dagger, but feel that Guice is more powerful and
> flexible.  Which is why we are investing time in making Guice more
> performant for our use-case.  We hope to make additional contributions in
> the future to further close that gap.
>
>
>
>
> On Tuesday, October 21, 2014 2:14:22 PM UTC-7, Stéphane NICOLAS wrote:
>>
>> No, we didn't compare them yet.
>>
>> For sure, RG + RoboBlender decrease the amount of processing needed to
>> compute injection points, but still a good part of it is done at runtime.
>>
>> Nevertheless, we think it makes a good compromise in terms of simplicity
>> and performance to use Guice + Blender on Android.
>>
>> S.
>>
>> On Tuesday, October 21, 2014 5:08:27 PM UTC-4, Sam Berlin wrote:
>>>
>>> This is interesting.  Have you compared the results to Dagger (Dagger1
>>> or Dagger2)?  Dagger is explicitly built with Android in mind, and shifts
>>> the processing to compile time.
>>>
>>> sam
>>>
>>> On Tue, Oct 21, 2014 at 5:04 PM, Stéphane NICOLAS <steff....@gmail.com>
>>> wrote:
>>>
>>>> Hello all,
>>>>
>>>> Mike Burton (the author of RoboGuice
>>>> <https://github.com/roboguice/roboguice>, a version of Guice adapted
>>>> to Android) and I have been working on a new annotation processor for
>>>> Guice(named Blender).
>>>> We have been working hard on this and, in RoboGuice, we gain from 30 to
>>>> 70% gain in speed and around 30% gain in memory footprint for our apps.
>>>>
>>>> *We would like to submit the idea of Blender to the community
>>>> of Guice devs in order to have your feedback on this, and as we hope
>>>> thatBlender can become part of the official Guice.*
>>>>
>>>> Here are some *slides* to explain why and how we did it :
>>>> https://speakerdeck.com/stephanenicolas/blender-boosting-guice-with-
>>>> annotation-processing
>>>>
>>>> We have currently *forked Guice* and tried to make something close to
>>>> a *PR* for it :
>>>> https://github.com/stephanenicolas/google-guice/tree/PR-blender
>>>> (Please ask us where to get the latest version, we try to stick on
>>>> guice 4 changes)
>>>>
>>>> We are very excited to submit Blender, and we are very open to modify
>>>> our implementation to make it fit in Guice and we are eager to get
>>>> feedback on it.
>>>>
>>>> Thanks in advance,
>>>>  Stéphane
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "google-guice" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to google-guice...@googlegroups.com.
>>>> To post to this group, send email to google...@googlegroups.com.
>>>> Visit this group at http://groups.google.com/group/google-guice.
>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>> msgid/google-guice/9cd1683f-0545-4687-b824-0a0cfd7a9f31%
>>>> 40googlegroups.com
>>>> <https://groups.google.com/d/msgid/google-guice/9cd1683f-0545-4687-b824-0a0cfd7a9f31%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>  --
> You received this message because you are subscribed to the Google Groups
> "google-guice" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-guice+unsubscr...@googlegroups.com.
> To post to this group, send email to google-guice@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-guice.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-guice/67524038-b76f-4979-9bf9-27b1a04c3ce9%40googlegroups.com
> <https://groups.google.com/d/msgid/google-guice/67524038-b76f-4979-9bf9-27b1a04c3ce9%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"google-guice" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-guice+unsubscr...@googlegroups.com.
To post to this group, send email to google-guice@googlegroups.com.
Visit this group at http://groups.google.com/group/google-guice.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-guice/CAHsNDCS9W3WemM9Lbu008pvprykKFjXxdSONuUipiOwz%2B9Tm3Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to