Renovating Jython: a strategic imperative

I always found Java boring, .. never really understood how people could get all fired up about it :-)

When it comes to programming, however, Java is the undisputed present day “king of the hill”. It has a huge community and a lot of cool tools (e.g. Lucene and ANTLR just to mention a few) that I would love to use in my own projects.

Problem is: I don’t fancy the prospect of writing Java code. Having used Python almost exclusively for the last two years I came to appreciate dynamic languages and loathe going back to statically typed programming.

Maybe Groovy can fill the gap: it appears to be dynamic in nature while allowing easy access to all the Java goodies. It has some potential and I am still exploring it.

All things considered Jython would clearly be the best contender if it were not for the fact that it is quite outdated (when compared to CPython).

My sense is that a lot of developers and companies would embrace Jython (and thus Python) without any hesitation if provided with a modern and more up to date implementation. The Jython renovation effort is thus a no-brainer and a strategic imperative for the entire Python community.

We should not allow others to outrun us in this important “market segment”. Let’s get our act together and lend the Jython folks a helping hand!