I agree that suggesting to companies that they retrain their
developers in Objective-C is a bit much because it is only used for
Cocoa applications
If you are going to do any Cocoa development (or related frameworks)
learning Objective-C/C++ is trivial compared to learning the Cocoa
APIs and related programming patterns/paradigms. Seriously in all the
groups that I have worked with, who started to do Cocoa development,
learning Objective-C was the least of the ramp up time involved
(often
the Java folks pick it up the fastest in my experience).
Sure, but try suggesting that to a company, especially since
Objective-C is a single-platform language. I agree learning Cocoa
is huge compared to Objective-C, but my suggestion is that the
business world is looking for a more gentle transition to the OS X
world, like wheel in the box and it just works.
Thing is, if they are doing Cocoa, they are already doing a single
platform system. The overhead of having to pick up objective C,
python, or ruby is pretty small compared to the overhead of learning
the quite massive Cocoa APIs.
Apple does provide a C api, called Carbon. I am not that fond of it,
but many developers are.
I do think Apple should provide java apis for more of their stuff,
but I kinda agree that Cocoa/Java was not a happening thing. (In
other words, exposing auth services with a Java API would do me more
real good than exposing the entire Cocoa API in a half-assed way.) I
suggest that if you agree about specific APIs, file bugs asking for
the exact API you want. Might never happen, but then again...
Scott
_______________________________________________
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
