On 2/5/08 11:39 AM, "Paul Elschot" <[EMAIL PROTECTED]> wrote:
> ... I don't want to spend time learning
> yet another programming language.
I was very impressed at how easy Groovy is to learn for a Java programmer.
Certainly much easier than Python (which you already know, of course).
>> b) related to (a) is the fact that jython is like a python time capsule.
>> Many of the features that make python attractive are missing from jython.
>
> For me, that is limited to the with statement and conditional statement
> in Python 2.5 that are not in Jython 2.2.
Comprehensions, dates, regex differences, yield and a bunch of other things
for me. I found that I had to worry about portability from current python
scripts quite a bit.
>> c) Groovy's integration with java is far superior to Jython's. Jython can
>> call java, but java has more trouble calling Jython. With groovy, the
>> interface is completely transparent in both directions.
>
> That's an advantage and a disadvantage: more distance from java means
> easier programming, allthough probably not much.
I didn't find that to be true at all. Groovy definitely has gotten this
very right.
> Then calling back into Jython is not an issue, also because inheritance
> from Java works well in Jython, despite the distance.
But in writing map-reduce frameworks, I care a LOT about how easy it is to
call into the scripting language. I also want to be able to very easily
avoid crossing the boundary. That is relatively trivial in Groovy, hard in
Jython.
