4 ms·
He claims that Apple doesn't like Java because it doesn't lock you to their platform. But Apple worked very hard to support Java as an alternative to Objective
by ams6110 16y ago
He claims that Apple doesn't like Java because it doesn't lock you to their platform. But Apple worked very hard to support Java as an alternative to Objective C, they basically ported (or tried to port) the entire API to Java but it never really got traction. I'm not sure whether it was because all the folks who were early developers for OSX came from a NEXTSTEP background and already had a legacy in Objective-C, or whether the message-based method invocation of Objective-C was just more flexible, but for whatever reason it turned out to be a dead end.
- pkaler 16y agoYup. Apple stopped supporting the Java to Cocoa bridge because developers weren't using it. It is a huge uphill battle trying to make an App written in Java look good and run with a native feel. Apple doesn't like Java on the desktop because Apps look like this: http://twitpic.com/2djc4u http://twitpic.com/2djc4u Apple still uses Java on the server. For example, the iTunes e-commerce back end is written in Java.
- pvg 16y agoApps written in Java using the Cocoa bridge did not look like that, they looked exactly like Cocoa apps. Pretty much the point of the bridge, its eventual failure notwithstanding.
- jsz0 16y agoThere are some success stories. Cisco uses it for their ASDM client: http://imgur.com/hvGxp.png http://imgur.com/hvGxp.png
- stevejohnson 16y agoYeah, but look at those awful buttons and the weird nonstandard border in the top half.
- cubicle67 16y agoApple ported WebObjects to Java; a massive task
- protomyth 16y agoThe Java bridge had issues because of the dynamic nature of Objective-C.