Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Thousands of education, scientific, engineering, mathematics, and other vertical market applications that you've never heard of and wouldn't understand.


You couldn't have just left it at "Thousands of education, scientific, engineering, mathematics, and other vertical market applications"?

I wasn't attacking Java.
 
Apple doesn't mandate what programming language, toolkit, or runtime environments you can use (yet, except in the App Store), so I'm not sure what "official" means here, but...

They don't today, but for several years, Java was an official alternative to Cocoa for OS X development.
 
They don't today, but for several years, Java was an official alternative to Cocoa for OS X development.

Like I said, you're comparing apples to oranges. Cocoa is a framework/toolkit. Java is a programming language. Java was never an "official alternative to Cocoa," nor does that really make sense to say. Apple once produced Cocoa bindings for Java that allowed to to use Java instead of Objective C (for Cocoa programming) if you preferred. Few people used this (and it was always awkward), and Apple no longer supports it. This is probably what you're referring to. For the record, I tried this once--it wasn't horrible but wasn't really easy to manage.

Of course, Java provides Swing and other UI toolkits of its own. I suppose you could say they were "officially supported" in that Apple insisted on making the JVM, including the Swing implementation, instead of Sun/Oracle, but it's still not accurate to say that this was an "official alternative to Cocoa" since you could still use third-party bindings (not sure if anyone's bothered to write a Java one) or integrate in other ways.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.