Besides, Carbon is
conceptually closer to WinAPI so it is somewhat easier to implement
the company's crossplatform code base if the underlying language is
C/C++ and if Carbon is involved on the Mac side. Besides these people
might say that "we'd prefer Carbon/C++ because no one in our otherwise
PC-based company will be able to code review your Objective-C" (that's
from personal experience) and they are "right" to extent - they pay
money for what they want to have.
That's a great point. What happens when our PC engineers need to
duplicate a feature on Windows for which our Mac engineers have
already written? With our current team, I develop all new features,
write the cross-platform code and the Mac UI, then the PC side gets
added. If all our Mac code was in Obj-C, how would the PC guys read
it to be able to see how I did things? I sure wouldn't want to be a
PC guy being told that I had to learn Obj-C just so I could
understand it. Then there are the guys who work on the server
product, which is also based on the same cross-platform code and has
Mac, Windows, and Unix versions.
Besides, being cross-platform means inheriting cross-platform C++
classes in a lot of cases. Obj-C can't inherit from C++, right?
_______________________________________________
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
