Re:Java.next() - The Groovy Programming Language
by drivebyacct2 on Saturday May 07, 2011 @03:08AM
(#2523345)
Right, that's my point. Why is Groovy "java.next()" and not one of the other many languages that run in the JVM?
edit: Maybe I've misinterpreted the headline to mean more than it should.
Re:Java.next() - The Groovy Programming Language
by zem on Saturday May 07, 2011 @05:49AM
(#2523519)
"In a series of articles labeled “Java.next()” I’ll be discussing modern alternatives to the Java programming language."
i.e., they're all labelled "java.next()"
Re:Java.next() - The Groovy Programming Language
by vorg on Saturday May 07, 2011 @05:41AM
(#2523506)
Groovy is different to Scala and Clojure, the other two languages in that blog series, in that Groovy uses the Java classes whenever possible, and isn't intended to run on the CLR. Scala and Clojure were both intended to be dual VM from the start. Rich Hickey says the 'C' in Clojure is for CLR and the 'j' is for JVM. Scala and Clojure have their own collection classes runnable on either VM, while Groovy is JVM-bound.
And of course Python and Ruby do it differently, having J- and Iron- implementations, each at different versions to the primary implement and each other.
https://bitbucket.org/puffnfresh/hello-jvm/src/f78a6a2312ae/...
Interoperability is actually very nice for most languages.