« Ah, that's your name then | Main | Coathangers »


Towards Jython 2.2

Jython, lest you do not know of it, is the most compelling weapon the Java platform has for its survival into the 21st century:-)

A (non-technical, but important) argument against Jython is that it has looked moribund for some time now. I guess this release knocks that on the head.

The (non-technical, but important) other is that 'you can't sell scripting languages into the enterprise'. Maybe so, but you sure can sell results into the enterprise. Let's face it, even Sun recognise now that Java is not a good fit for scripting, and that scripting is a valuable activity in enterprise work, hence the will to support new languages running on the JVM.

In Java, the only other viable option to Jython seems to be using XML as your scripting language. But is programming in XML really in you and your customers best interests? Read Jonathan Simon's article, which is turning heads, and judge for yourself.

August 1, 2003 11:11 AM


Carlos Villela
(August 1, 2003 12:34 PM #)

I agree with you here - scripting is a valuable tool for the "enterprise", but your view that Jython is the only viable option is a little bit flawed. I've been using other scripting languages, such as JavaScript (with Rhino) and BeanShell, and so far they're doing the job just fine :)

Joey Gibson
(August 1, 2003 01:31 PM #)

There's also JRuby which is a Java port of the wonderful language Ruby. http://jruby.sourceforge.net Just like Jython it's stalled a bit, but work has restarted as of late.

(August 1, 2003 04:31 PM #)

I've been using Beanshell too for some time. The ability to telnet into a remote jvm and muck about with stuff while the app is running makes it a great (but scary) debugging tool.
"With great power comes ..."

Miles Sabin
(August 4, 2003 11:19 PM #)

Oh, come on Bill. Jython the only scripting language for the Java VM?


Trackback Pings

TrackBack URL for this entry: