I've seen several statements in this thread to the effect of Cocoa
"is not cross-platform", thus it's bad.
I fail to see how this is relevant to the subject at hand: no 64
bit Carbon UI code in Leopard. If you are writing native Mac OS X
UI code, it's platform specific by definition regardless of which
language or API you use.
The argument is that the developers on our Windows team won't be
able to look at Mac code to see what logic was used when porting UI
first written on the Mac in Cocoa, because they'll first have to
sit there and stare at what looks like garbage with way too many
square brackets scattered about. It's one of the many bad things
about Obj-C in general.
Exactly. Cocoa and Obj-C may be vastly superior to Carbon and C++ for
application development, but if you have Windows guys who aren't
about to learn Cocoa to facilitate cross-platform work (and I suspect
more aren't), and those guys are calling the shots (as they often are
since sales of the Windows product are so much larger), all that
Cocoa wonderfulness is irrelevant.
Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
