Re: Cocoa and future
Re: Cocoa and future
- Subject: Re: Cocoa and future
- From: Jens Alfke <email@hidden>
- Date: Fri, 20 Feb 2009 08:17:29 -0800
On Feb 20, 2009, at 4:08 AM, john smith wrote:
So, you mean that it will be as now, except carbon views will not be
supported?
"Carbon" is kind of a fuzzy term. What's being dropped in 64-bit is
the High-Level Toolbox, the UI layer of Carbon. CarbonCore is still
supported — it's a key part of the OS underpinnings, and a lot of the
Cocoa frameworks are based on it.
And CoreAudio itself is not Carbon. (Some people use "Carbon" to refer
to anything in the OS that's not either Objective-C or derived from
Unix, but that's not accurate.)
P.S. Let's drop the sales pitch :-). IMHO cocoa is a pain in the
behind, and much much slower for me to work with, esp. seen from a
cross-platform point-of-view. But that's just my 2 cents
So sales pitches are out but bashing is OK? o_O
If you see Cocoa as more of a pain than Carbon, that's just the
learning curve you're looking at. It is much, much more efficient for
writing GUI code than HLTB. (I spent 12 years programming the Classic
OS, then learned Cocoa and never looked back.)
I don't see why the cross-platform issues are any greater. Both Carbon
and Cocoa are Mac-specific APIs. Both of them can call into cross-
platform code just fine. If your cross-platform code base is in C++,
just use Objective-C++ (.mm files) for your Cocoa code and it can work
with C++ without any problems. (The last project I did for my previous
employer was cross-platform and involved just this kind of setup, with
cross-platform C++ interfaced to Obj-C.)
—Jens
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden