I haven't really used Cocoa, but here's my understanding:
Originally posted by danengel:
1) Is one of the API's faster than the other?
In theory, no - in practise, Cocoa apps tend to run a lot quicker because more of your work has already been done more efficiently in the libraries. If you started writing your own hashtables, you'd be a long time at it to make them any good. Use Cocoa, and they're provided (i think).
2) Is one of them "better" than the other or is each suited for a specific purpose?
Specific purpose. Carbon is particularly useful if you have existing code, particularly in C++, that would need to be part of the new App. It's also better if you want to port the program to another platform afterwards.
Cocoa is better if you have a clean slate to write a new program.
3) Is it possible that Carbon will become unsupported in the future?
Unlikely, at least this decade. Classic may go in a year or two, but considering the next Office is Carbon and won't come out until October (ie, March) they can't deprecate it any time soon.
And something else, concerning my current (OS 9) project:
4) Which one is better for integrating low-level, assembly routines?
either of them can use plain old C, which is what you'd best use. It makes no difference.
Top
