From: Robert W. B. <rb...@di...> - 2000-11-28 19:29:11
|
[On Tue, 28 Nov 2000, Finn Bock wrote:] > The real problem with this approach is java1 compatibility. It is an > unmoving requirement that jython can be used in a java1 browser like IE. This 'unmoving' part makes me curious. I would like to hear more of the reasoning behind it. The conditional sounds like: 1. We must support Java1 browsers, so 2. we must support Java1 compatibility. This often repeated scenario assumes there's no other way to support these browsers, and there is no other reason given for Java1 compatibility. However: 1. Java2 plug-in is intended to support such browsers, and 2. it seems there must be other reasons involved in choosing Java1 compatibility, so 3. both antecedent and consequent of the conditional seem arbitrary and flimsy to me. Does the Java2 plug-in not work well? Is there a legal implication to requiring the plug-in that bothers people? Are there essential tools other than browsers that lack 1.2 drivers/support? Are embedded or real-time-Java ventures working only with Java1? Does Java1 compatibility increase chances of eventually working with alternative JVM's? Without additional reasons, someone could propose: *"The Java2 plug-in enables Java2 for most broswers" *"Java1 compatibility is not essential for Java1 browsers because of the Java2 plug-in" *"Unless other valid reasons are proposed, using Java2 with the plug-in is reasonable." I expected more of a discussion after last years conference. See: http://www.python.org/pipermail/jpython-interest/2000-January/005222.html This is just sincere curiosity- not a proposal, and I look forward to hearing comments. -Robert |