[Apple] should switch from Objective-C and its runtime to a fast, clear, mainstream language like Java and the Java VM. BTW, when I say Obj-C, I mean Obj-C + the Apple Cocoa libraries (or even the NextStep ones I presume).
Jerakeen rightly points out that there's not that many good Java-based OS X apps out, but I wouldn't necessarily put the lack of such apps being down to Java being slower. My experience while developing my masters thesis last summer was that while there was (is) in principle Java support for the Cocoa API, what was there was decidedly lacking: there wasn't even any support for AddressBook at the time. I don't think it's so much Java support being inherently bad (indeed it was pretty easy for me to knock my project up) on OS X as Apple deciding to emphasise Objective-C and devoting more resources to making sure ObjC works better. It doesn't help either that the implementation of Java on OS X has been lagging for a while.
39 comments and trackbacks