I'll have to take you up on the comparison you made between groovy and orher java scripting languages, Ian, as I don't see any of the key selling points as being unique to groovy.
Beanshell must have the least special syntax of them all, as it's possible to interpret most java code directly via beanshell, including support for inner classes, allegedly (haven't tried this one myself, I admit). Admittedly, some languages such as python will look different at first
exposing bean-like properties directly
jython can do this, and also applies a similar 'shortcut' syntax to event listeners, making gui coding very concise, on a par with your swingbuilder example's actionPerformed syntax
a well-known feature of javacript
pre-compiling scripts into bytecode
both jython and rhino have had this capability for some time. Like groovy, both require bundling of the scripting runtime at deploy-time, but performance increases are improved
ruby supports these (I don'tr know jruby, so can't comment any further)
would the BSF scriptlet tag be worth a mention here, as it allows just about all the other scripting languages mentioned be easily embedded into JSP's?
I've nothing against groovy, and a great deal of support for jvm scripting languages of all flavours. As the new kid on the scripting block, I've heard a lot about groovy, but didn't find your article provided me with a compelling reason to switch away from jython, beanshell or rhino.
Thanks for writing,