RE: Carbon vs. Cocoa
RE: Carbon vs. Cocoa
- Subject: RE: Carbon vs. Cocoa
- From: Brant Sears <email@hidden>
- Date: Wed, 11 Jun 2003 11:21:10 -0700
>
Realizing that Cocoa and Carbon are APIs, they
>
ultimately define the use of ObjC and C and thus the choice between
>
languages.
Objective-C, like C++ is a superset of C. If your project involves much back
end code, you can separate the GUI and write portable C or C++ code for the
back end.
The front end won't be portable anyway. (Unless you use Qt. It is expensive
and you do take a speed hit with it.)
>
Our current implementation uses Cocoa, though the thought is that using
>
Carbon would provide speed increases, ease in porting to Windows, and
>
less languages used throughout the system.
Carbon won't help you port to Windows - writing a portable back end will.
I wrote an app recently that had a significant back end. I wrote mostly in
C++. I did the front end in Cocoa using Objective-C++. It was ported to
Windows really fast Win dev had my backend compiling in VC++ in just hours -
mostly involving creating the project. He did a front end using MFC and we
were done in a month.
Unless you are doing something realy unusual (i.e. I would ask you to prove
the speed increase), I would not expect much of a speed increase from
Carbon. I use Carbon - I programmed for MacOS since system 7. However, for
new work where I don't have to support MacOS 9, I will pick Cocoa.
Brant Sears
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.