The fact that Java 1.6 is not ready for leopard is not the problem. It will, given that it was already available for tiger. Surely, Apple want it to take advantage of the leopard features, and delaying the release of Leopard just for this would be non-sense. If you are a Mac developer "sensu-stricto" (i.e. a Cocoa Developer), possibly you couldn't care less about Java.
However, the real problem is that Java on Macs (even in the "classic" era) has always been in late. I am a Java developer (and also a Mac fanboy) and this issue always prevented me to adopt MacOSX as main developing system. Even if I don't need the latest JDK for the development, the fact that I can use it and try it only months after it has been available on the other platforms makes me a bit uncomfortable. And, finally, how long did it take to have Java3D available on Mac?
Register
Annoying
The fact that Java 1.6 is not ready for leopard is not the problem. It will, given that it was already available for tiger. Surely, Apple want it to take advantage of the leopard features, and delaying the release of Leopard just for this would be non-sense. If you are a Mac developer "sensu-stricto" (i.e. a Cocoa Developer), possibly you couldn't care less about Java.
However, the real problem is that Java on Macs (even in the "classic" era) has always been in late. I am a Java developer (and also a Mac fanboy) and this issue always prevented me to adopt MacOSX as main developing system. Even if I don't need the latest JDK for the development, the fact that I can use it and try it only months after it has been available on the other platforms makes me a bit uncomfortable. And, finally, how long did it take to have Java3D available on Mac?