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 2221
To view parent comment, click here.
To read all comments associated with this story, please click here.
Tyr.
Member since:
2005-07-06

I think is a good idea. I'm very surprised by the "Virtual machine insanity" that has spreaded in the last years, of course, VM have its uses, but every excess is bad and they also have its disadvantages. If I can choose I allways prefer to use platform native apps.

Really? Think about this : Apple is going to be supporting 2 different architectures at the same time. Objective-C apps are going to break, no matter how well coded. Then they will need to be compiled to "fat" binaries.
The java apps won't have all these problems, it's a perfect example of one of the core benefits of java.

Reply Parent Score: 1

Member since:

"Objective-C apps are going to break, no matter how well coded. "

What? Ever heard about Rosetta?

Reply Parent Score: 0

Tyr. Member since:
2005-07-06

"Objective-C apps are going to break, no matter how well coded. "

What? Ever heard about Rosetta?


See Segio's answer. Plus Rosetta won't run all apps, like those that depend on altivec for example. No emulation layer is perfect, much better to have your code written for an unchanging virtual machine.
Besides, my original point was that the java code doesn't have all the endian issues etc. you have when porting objective-c code to run on both architectures.

Reply Parent Score: 1