Ryan Heise wrote:
> I agree that compatibility is an issue worthwhile discussing. I just
> have a few constructive things to add to the discussion:
> I don't see the point in bashing Sun, but I do see that compatibility is
> something that we should consider. It is conceivable that Sun could, for
> example, change the JVM specification making new JVMs incompatible with
> older JVMs, or that they could make incompatible changes to the JDK
> libraries. However, call me short-sighted but I just don't think it is
> something worth worrying about now -- at this point in the project
> timeline. Someone will need to think about these issues in the future.
worth worrying about, but on JOS general mailing list please
> Actually, you sound quite keen. Why don't you come up with a proposal?
Gilbert, he is quite correct. maybe you could get JDK 2.0 (or Java 3 or
Java:the next genertation, or whatever Sun decided to call the bloody
thing) to only put the essentials in the java package and the rest in
javax where it should be, maybe you could even talk them into
multiprocess VM's.
But please from now on discuss this is on the JOS general mailing list,
I dont want to remove anyone. last thing I want to be is censor morum
people; this is the *last* warning.
Cheers,
DigiGod
_________________________
[EMAIL PROTECTED]
AIM:DigiGod 86
_________________________
Quote of the Moment:
Thus spake the master Ninjei:
"To the intelligent man, one word, to the fleet horse
one whip, to the well-written program, a single
command"
_________________________
Prank of the Moment:
Using the conferencing feature of your office phone, dial
one Induhvidual, then while it's ringing dial another and
conference them together. Put your own phone on mute
and listen to see how long they'll make small talk before
figuring out that neither one placed the call.
O-
_______________________________________________
UI maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/ui
