I get the impression that the J2EE world is starting to go ballastic 
over Jython. JRuby gets some mention, but not that much, and I get the 
impression that the long term prospects of JRuby are a bit mixed. For 
this reason, I felt compelled to learn some Jython so I could use a 
modern language in my day-to-day J2EE work.

Unfortunatly, I really can't stand using Python. The selfs, method 
__protection__ mechanism, and lack of expression-orientation (unlike 
Lisp and Ruby) make me weep. I'm still plinking at it here and there, 
giving it a chance, but my mindset is not improving, and I'm starting to 
think Python claims of readability are only relative to Perl- I find 
Java/C/C++ easier to read. But that's really irrelevant to this point, 
outside of my personal motivation for looking at JRuby more seriously.

So now  I'm trying to use JRuby, and it's much better then I expected. 
However, I'm still concerned about:
 1. it's robustness and how it impacts my chosing to use it, and
 2. it's impact on Ruby longterm due to prevalence of Jython.  I get the 
impression that Jython is becoming almost the defacto J2EE scripting 
language, with Groovy possibly taking off when it's more mature (is it 
just me, or does Groovy look a lot like a Ruby clone with a bit of Java 
baggage left in for more seamless interoperability?).  Where Jython has 
followed Python into general usage, that could change with Jython being 
the reason people use Python.

Not sure what point is...I guess I'm looking for some 
experiences/ideas/feedback. I think dynamic JVM langauges are going to 
become an essential part of enterprise Java, and I'm hoping I don't have 
to use Jython on my next job. Those underscores and selfs- how can 
anyone stand it? And the lack of expression-kindness.

Thanks,
Nick