On Feb 19, 3:38 am, Robbie Vanbrabant <[email protected]> wrote: > This is very cool, but wouldn't it be a better long term strategy to > factor this AOP / no AOP thing into the code? > I mean, ifdefs seem to be an excuse not to bother with OO goodness :)
I definitely prefer OO goodness, and this decision was not taken lightly. Dependency injection is extremely popular on the server, but we'd like to see more of it on the desktop, in the browser, and on mobile devices. The AOP-free version of Guice is built with Android in mind. It saves about 20% in .jar size, which is significant for a space-limited phone. Having a separate, AOP-free .jar makes it more explicit which APIs are off-limits. For example, code that uses bindInterceptor() doesn't compile! This sucks, but it's much nicer than an UnsupportedOperationException. I'm intending to trim down our Google Collections dependency next, which should also help in this effort. The full feature matrix is here: http://code.google.com/docreader/#p=google-guice&s=google-guice&t=OptionalAOP --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-guice-dev?hl=en -~----------~----~----~----~------~----~------~--~---
