I am entitled to my opinion. I believe the JCP vote was correct. Guice is no fork-join. Bob is no Doug
Badgering Reiner? Stick with your obfuscative programming ideas that no one uses and then write some more random posts I prefer to be honest and spot on the mark in respect to this thread. On Nov 20, 3:35 pm, Reinier Zwitserloot <[email protected]> wrote: > So, you have an opinion. You're entitled to it. What you're not > entitled to is badgering a contributor into agreeing with your > opinion. > > On Nov 20, 5:34 am, Liam Knox <[email protected]> wrote: > > > JCP vote. > > > Google collections is a fantastic AP and I like MapMaker also. You could > > argue it is pushing too far towards caching though. Why I cant do > > Maps.newConcurrentHashMap() is a more pertinent question. > > > Guice has benefited the community also and we are all thankful to you, I > > hold my hat up for that, but I maintain Guice's most important role has > > been in influence rather than adoption. Where as Spring has basically ripped > > apart this nonsense of J2EE, Guice has influenced the direction of IoC and > > Spring adoption of better annotation/Java based configuration. > > > On Sat, Nov 20, 2010 at 1:16 PM, Bob Lee <[email protected]> wrote: > > > On Fri, Nov 19, 2010 at 6:35 PM, Liam Knox <[email protected]> wrote: > > > >> You did help create google collections. From my understanding around the > > >> Immutable idioms. Though I doubt not the great and profound idea to > > >> base it > > >> all on Iterable. This is the key to the APIs success. > > > >> But please correct me if I am wrong. > > > > I created MapMaker among other things. I didn't have much to do with the > > > immutable implementations, but I think they're awesome. > > > > Best thing Guice did was introduce annotations in the IoC domain. In your > > >> honesty you will concede this. > > > >> Guice was never Spring. Spring was an absolute Game Changer for > > >> application development. > > > > Guice benefited from Spring's experience. > > > > The best parts of Guice are its clean, intuitive API, its attention to > > > detail, and its efficient implementation. The annotations are great, but > > > so > > > are provider methods. > > > >> Again I think this vote went in the best interests of everyone. > > > > What vote? > > > > Bob > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "The Java Posse" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<javaposse%2bunsubscr...@googlegroups > > > .com> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/javaposse?hl=en. -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
