On Fri, Jul 29, 2011 at 4:07 AM, Russel Winder <[email protected]> wrote:
> On Thu, 2011-07-28 at 15:03 -0700, clay wrote:
> [ . . . ]
[snip]
> [ . . . ]
>> The new file API looks very nice and clean and adds important
>> functionality. InvokeDynamic is behind the scenes, but that should be
>> a major performance advantage for Groovy, Ruby, and Python work (I've
>> heard Scala wouldn't get much gain since it is statically typed).
>
> It is not entirely clear that invokedynamic is actually good for
> languages like Groovy and Jython. All the development was done for
> JRuby, and I believe it helps that language a lot. Much of the
> muttering in the Groovy and Jython community seems to indicate that the
> overheads of using invokedynamic are potentially worse than not using
> it.
>
> It is a shame that the hype around invokedynamic has caused people to
> fall into the belief that it "should provide major performance advantage
> for dynamic languages" when actually, as yet, we have no idea whether it
> will even be particularly useful for some of those languages.
This year's JVM language summit, held earlier this month, could be
summarized as "cool things to do with invokedynamic." The slides from
the talks have been posted
http://www.wiki.jvmlangsummit.com/Main_Page
JRuby along with the implementations of many other languages were discussed.
It is known and acknowledged that invokedynamic is not fully optimized
in JDK 7 GA; work is continuing to improve the performance of its
usage.
--
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.
