Jul 08
Eric Gunnerson was in the same position that I was in when I went to Microsoft TechEd a month ago. It was my first time at a Microsoft conference, and I was actually impressed.
Eric seems to be impressed with some parts of JavaOne too, including the community aspect that Java has (which is of course a double edged sword).
It is especially interesting to read about his thoughts on Groovy and AOP.
Groovy is a new scripting language (well, they call it an
July 8th, 2004 at 1:57 pm
Operator overloading? Is that really in there? My interest in Groovy keeps going down as I hear more about it…
July 9th, 2004 at 3:00 am
>> I didn’t see a lot of evidence of rigor in the language design.
And this is from a guy who writes perl – LOL! :)
July 9th, 2004 at 3:04 am
>> Operator overloading? Is that really in there? My interest in Groovy keeps going down as I hear more about it…
Relax Jason – operator overloading can be used for good :)
We use a limited form of operator overloading to allow, for example, the [] subscript operator to be used with Maps, Lists, Strings and ResultSets to implement polymorphic index lookup just like Java supports with the Array types.
i.e. we allow you to perform index operations just like you can in python & ruby.
Did you know that both Ruby and Python both implement operator overloading for such things as the [] notation? We’re just reusing good established practice.
July 12th, 2004 at 2:38 pm
I would like to here more about your thoughts of JavaOne