On Aug 23, 2006, at 12:30 PM, Diez wrote:

 - ruby has no notion of java-library support. So if anything lures java

developers from J2EE-land to rails, its the framework itself. Which, by my

standards, is at least met if not excelled by TurboGears and Django. So

it's marketing, but of a different kind, we need.


People move in crowds, and although the initial draw to Ruby was Rails, that translated into "Ruby is the next Java", which is a force to be reckoned with in and of itself.

I think the fact that Ruby doesn't have a Java library migration path is exactly why JPype is a great opportunity for Python.  Django and TG will not (regardless of their technical merits) catch up to Rails in terms of broader mindshare for years, if ever.  Having them (and pylons! :-) is obviously fantastic, but opening up a new front of comparison where Python is the obvious choice is where Python can score points, rather than try to catch up.

 - jython, after a period of seemingly inactivity, makes huge progress

towards python2.2 and python2.3. Which will open up new possibilities just

the other way round: use existing, powerful python libraries written in

post-2.1 from jython, neatly integrating java and python. Now there is

jRuby trying to do the same for ruby - but I never heard of it before

(googled it for this post), so it seems not to be as important as jython

certainly is


You bet, Jython is a great concept, and it's another arrow in Python quiver.  I don't think it comes close to nullifying JPype's potential to help Python's stature with Java developers, though -- it's orthogonal to JPype, and therefore complimentary.

Chas Emerick
Founder, Snowtide Informatics Systems
Enterprise-class PDF content extraction

-- 
http://mail.python.org/mailman/listinfo/python-list

Reply via email to