Linked by Andrew Youll on Sun 10th Jul 2005 18:22 UTC, submitted by anonymous
Apple In the latest update to the technical documentation available from ADC, Apple has published this note: "Features added to Cocoa in Mac OS X versions later than 10.4 will not be added to the Cocoa-Java programming interface. Therefore, you should develop Cocoa applications using Objective-C to take advantage of existing and upcoming Cocoa features".
Thread beginning with comment 2256
To read all comments associated with this story, please click here.
I'm surprised
by on Mon 11th Jul 2005 01:15 UTC

Member since:

I'll take it one step further and say that Objective-C is irrelevant. Name a framework to use with it when not on a Mac. It makes zero sense to write ObjC unless you are writing a Cocoa app, which is not exactly a ringing endorsement for a language. If I was writing a cross-platform app for Mac, Linux and Windows I'd be looking at C++ and Carbon long before Objective-C.

So this decision surprises me. If anything, I would have thought Apple would be moving off of ObjC and more towards Java. Of course, even better would be C# and taking on the CLR from Mono, as another poster mentioned.

Reply Score: 0

RE: I'm surprised
by mini-me on Mon 11th Jul 2005 01:44 in reply to "I'm surprised"
mini-me Member since:
2005-07-06

why would apple move to C# ? It's a microsoft product.
Why would apple move to mono? It's an open-source language which they have no control of - which is important when you are developing for your own platform!


For those who don't remember, back in the days of rhapsody, apple had yellow box for windows NT - you were able to run cocoa apps on windows! If apple wanted to they could have cocoa apps running on windows without any problems. Who knows - maybe apple has kept yellow box on the back burner just like they did with os x on intel.

Reply Parent Score: 2

RE: I'm surprised
by on Mon 11th Jul 2005 02:51 in reply to "I'm surprised"
Member since:

> It makes zero sense to write ObjC unless you are writing a Cocoa app, > which is not exactly a ringing endorsement for a language.

ObjC w/o Cocoa is still ObjC with all the dynamism, etc. present in the language. The lack of Cocoa takes nothing away it. Your criticism of the language is not well founded.

Reply Parent Score: 0