On Aug 23, 2006, at 12:30 PM, Diez wrote:
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.
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