From Java developer point of view I don't see any advantage of using Macs for Java development in X11, I might as well be using Ubuntu/Linux and have much better integrated development.
If all writing are jsp and J2EE stuff then all you need on your development machine is a local app server can run and locally debug/step/trace It is never going to invoke any part of the Java library that touches X11. The catch 22 with J2EE is that is layered on top of Java but the reality is that the vast majority of the GUI aspects of the library are never invoked in the "enterprise" java.
Sure if your IDE is also written Java that will have to interact with X11 but your "enterprise app" doesn't deal with it at all.
So why use Mac OS X ? Because when not writing code ... it is a better desktop. Unless you are some kind of obsessive compulsive... who cares if some of the windows are X11 ones and others are Cocoa ones and the screen widgets don't all match in color/texture. Frankly, in Linux desktops if invoke a variety of programs they aren't likely to either.
The advantage of using Mac for Java development was the tight integration between the OS and JavaVM - you really had to try hard to see the difference between Java apps and Native apps.
For the developer who is writting apps to deploy on desktop yes. But that isn't the majority of java coders.
It isn't so with Oracle VM on Linux and windows. And it can't be so with hypothetical Oracle JVM for OS X.
"Can't" is awfully strong to through out with no support. Pragmatically Oracle probably doesn't want to spend that much money, but can't ? Pfff, if it has been done, then it can be coded. It is just a matter of applying the resources. It isn't like Apple has sole access to magic fairy programmers that can do stuff no one else on the planet can do. Try "won't"
By the way it is not the VM that is the issue. It is is the bindings between Swing/AWT and the underlying graphics libraries. There are bound to be some semantic mismatches, but if work hard can minimize them.
http://www.developer.com/java/other...-and-SWT-A-Tale-of-Two-Java-GUI-Libraries.htm
Being Apple user for more than 20 years, I see this as Apple's stupidest move since firing Jobs back in 80s.
Come on? Pippin , $3K Newtons , ..... , this Spring killing off "all 3rd party libraries and only these 3 languages" on iOS (which has now partially retracted) , ....
More so, typical clumsy Apple stumbling around when it comes to developer technology.
Oracle may come out with a good Cocoa bound version over the long term. I just don't expect that to happen over the short term unless there has been a
ton of work done in secret for over last 6-12 months.
Since there doesn't seem to be organization between Oracle and Apple most likely stop gap OpenJDK will like be rolled out as interim solution along with the last Apple effort being stretched over a long period of time.