[muchfresh]

I am trying to decypher Apple's syntax/language intentions for Cocoa. Originially devloped in Objective-C Apple has since added support for Java. The catch is that not all the API are accessable using Java syntax. Additionally their is bridge code that may or may not impare performance but at least adds another layer of complexity.

WebObjects was orginally an outgrowth of Cocoa and likewise was based on Obj-C. Now with the next version is going to be a pure Java application.

On their web site Apple seems to push both Java and Obj-C equally. . Many developers scoff at the Java implementation. The O'reilly book on Cocoa is in Obj-C. The iServices courses are also in Obj-C. So on one hand it looks like Apple is moving towards Java. But they don't make it clear by offering so many resources in Obj-C.

I believe Apple would be well served by embracing just one standard with 100% energy. Clearly there are marketing advantages to make it Java. But maybe the technological advantages lie with Obj-C.

any ideas?

[davecom]

As your last sentence said. There are market advantages to supporting Java but technological advantages to Objective-C. Objective-C will always be the REAL Cocoa language since it goes back with the API to '89.

Dave

------------------
Think Different.