| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
The Cocoa-Java bridge going away is not really related to Apple moving Java forward on the platform. If I were to guess, the philosophy would be:
Apps that run only on macs should be done in Objective-C, because that is the best language for the platform, and certainly the most popular language being used. There are not many people using Java to make cocoa apps, because the main reason to use Java is cross- platform, and using Apple specific functionality from Java just doesn't make sense.
For people who are developing Java for cross-platform use, Apple still wants to be the development environment of choice, so they will work harder to move newer versions of Java onto the platform sooner, but if you want cocoa API's, use Objective-C.
To me, this is a reasonable philosophy. To give users the experience they want (and sells macs), the APIs have to expand and improve. To have a team of people dedicated to moving cocoa APIs to java is just not worth it to them.
Vince
_______________________________________________ Do not post admin requests to the list. They will be ignored. Java-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/java-dev/email@hidden
| References: | |
| >Apple should get behind Cocoa Java (From: Vince Marco <email@hidden>) | |
| >Re: Apple should get behind Cocoa Java (From: Terry Simons <email@hidden>) | |
| >Re: Apple should get behind Cocoa Java (From: Andrei Tchijov <email@hidden>) | |
| >Re: Apple should get behind Cocoa Java (From: Ken Anderson <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.