On Feb 26, 2010, at 3:48 AM, H. Gluender wrote:

> ...we are currently discussing programming languages that provide  
> unrestricted access to Apple's API, which will exclusively be Cocoa  
> in the future....


I would like to quote some short passages from "Learn Cocoa on the  
Mac" by Jack Nutting, David Mark and Jeff LaMarche. It was just  
published this month and has some interesting comments about C++ and  
Java in their "Future Paths": Chapter 17 pages 339 and 340. Talking  
about Cocoa in a Foreign language ( meaning something other than  
Objective-C ) he discusses which other languages have bridges to  
Objective-C and which do not. "...two of the biggest and most popular  
languages, C++ and Java, aren't among them". "why not? Without getting  
too deep: C++ and Java are just too inflexible. They don't have the  
sort of runtime introspection capability that's required for fully  
interfacing with complex Objective-C class libraries like Cocoa".  
"Maybe technically, Java has got what it takes." He goes on to point  
out Apple included a Java bridge for building Cocoa apps in the first  
versions of OS X but abandoned the project several years ago.

BTW: the chapter on Concurrency discussing use of NSOperationQueue and  
its evolution via Grand Central Dispatch is interesting and the first  
mention outside of Apple docs I've seen.


Brian S