On Mon, Oct 27, 2008 at 1:04 AM, Gili <[EMAIL PROTECTED]> wrote: > > Just as a side-note, why has Guice 2.0 gotten so fat? Guice 1.0 was > 540k. Guice 2.0 is 950k.
New features, and Google Collections has now been JarJar'ed I think. If Guice was my only dependency I wouldn't worry so much but this is part > of a growing pattern, the total of all my dependencies has grown into > the multi-megabytes. This makes life difficult for desktop > applications... > For desktop apps you can always consider using JarJar or ProGuard yourself. > This discussion is somewhat related to unbundling CGLIB from Guice > because my project already has it as an external dependency. And > surprisingly, CGLIB is itself a fat library compared to ASM... ASM > does a lot of difficult work compared to CGLIB which makes you wonder > why the latter is 3x larger! CGLIB is an abstraction. Abstractions mean more code, so it doesn't surprise me at all. Also, ASM is almost legendary for its size. Cheers Robbie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" 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?hl=en -~----------~----~----~----~------~----~------~--~---
