Design Element
Comment on "What is Cocoa?"
by Scott Stevenson — Oct 02
@Scott: Oh, and do developers really think that Core Image is part of Cocoa?

Yes, I think so. Cocoa and CoreImage are seen together so often that they are bleeding into each other.

@Nat: An avowed OS X programmer who can't or won't handle reaching into Carbon from a Cocoa app when the situation calls for it ought to stick to Realbasic and baking scones.

There are parts of Carbon that will be around until the end of time, but I don't think most folks are sitting down at this point to write a new Mac app which doesn't use NSApplication, NSView, etc. BareBones, for example, wrote Yojimbo in Cocoa.

That doesn't mean they don't use any Carbon code, it's that the application revolves around the Cocoa model (NSApplication, NSView) and likely calls into Carbon where it makes sense.

So the point is which framework is the primary model for your app, and whether you're using high level toolbox. As we've seen from oft-linked messages on carbon-dev, the high level toolbox will not be brought across to 64-bit.

@Blain: I'm secretly hoping that, even if it takes until 10.5.1 or 10.6, Carbon becomes fully 64-bit as well

Good luck with that. :)

I'd like to see Core Data get the NSString treatment, and become something accessable via Core Foundation by Carbon as well

I just don't think there's much demand for something like that, and it's a bunch of code to re-implement when Apple could be spending their time on new functionality. It's not clear who it would benefit.

Talking about Webkit in general, I'd say it's neither Carbon nor Cocoa

That's WebCore, yes? WebKit/WebCore is a bit of a different beast since it wasn't entirely home rolled and is actually present in projects that have nothing to do with Mac OS X.
Back to "What is Cocoa?"
Design Element

Copyright © Scott Stevenson 2004-2015