It is NOT suddenly vital. We deliver products in all platforms. In 1.6, we
are using decomposing and composing Unicode characters and it is not
available on 1.5. We couldn't back port a fix using this feature to earlier
released version of our product because we needed 1.6 and we couldn't
deliver the new build for mac.
-----Original Message-----
From: java-dev-bounces+slledru=email@hidden
[mailto:java-dev-bounces+slledru=email@hidden] On Behalf Of Bill
Janssen
Sent: Friday, October 26, 2007 2:09 PM
To: Tim Goeke
Cc: email@hidden
Subject: Re: Java on Leopard report
> My point: Apple had time to beef up other language support and if,
> in fact, resources where constrained, why devote time to Python and
> Ruby when Java is still orders of magnitude bigger?
Why? To quote Jobs' quote of Wayne Gretzky: "I skate to where the
puck is going to be, not where it is." There's lots of COBOL in the
world, too, and Apple's support for it is pathetic.
So how about a technical discussion here? I see little or no
technical advantage in the use of Java 6 on the Mac platform, barring
bug fixes. What in the world is in Java 6 that suddenly makes it so
vital?
Bill
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
