I think the difference is that PyPy exists, so people who just want "a faster Python" tend to go there, whereas in ruby-land JRuby gets the people who just want "a faster Ruby" as well as those who want Ruby on the JVM.
Honestly I wouldn't recommend trying to use Django on Jython (I'd be amazed if it all works), or really doing anything on either Jython or JRuby unless you're already familiar with all of the pieces. To understand and debug Jython properly you need a good understanding of both Python and Java. For a first JVM project, find something good and idiomatic in Java (I hear good things about Dropwizard) and use that.
This is why I am surprised it is to hear about Jython, even here, where the GIL is thrown as a topic routinely any article with serious use of Python comes up.
> I think the difference is that PyPy exists, so people who just want "a faster Python" tend to go there, whereas in ruby-land JRuby gets the people who just want "a faster Ruby"
JRuby, IIRC, hasn't been particularly faster than MRI since MRI 1.9-ish, though it still has the advantage of no GVL for multithreaded apps.
Well, yes. You look at my comments and see I am interested in a recent post bemoaning how to build the simplest REST services possible in Java. So I know the name of the game.
I just want to see how this works if django-jython wokrs at all.
Honestly I wouldn't recommend trying to use Django on Jython (I'd be amazed if it all works), or really doing anything on either Jython or JRuby unless you're already familiar with all of the pieces. To understand and debug Jython properly you need a good understanding of both Python and Java. For a first JVM project, find something good and idiomatic in Java (I hear good things about Dropwizard) and use that.