On 21 May '08, at 10:50 PM, Charles Srstka wrote:
What becomes the purpose of the Carbon File Manager, anyway? Cocoa's already got a file manager. And yet even after seven years, with all the new APIs, new language features, and new paradigms that have been added to Cocoa, its file manager still has absolutely no support for forks or anything non-path based.
It's not Cocoa's goal to provide Objective-C APIs to every single feature of the system, just to the most common ones that are used in applications. If you compare <Files.h> with NSFileManager, it's like night and day — the former is an enormous API (even if you filter out the old deprecated functions) that provides a lot of functionality that isn't present in the latter. And vital functionality too, for the OS as a whole, even if most apps don't need it.
Similarly for LaunchServices vs NSWorkspace, or Quartz vs NSGraphicsContext/NSBezierPath, or NSStream vs CFStream vs BSD sockets. In fact it's not really "vs". They both exist, and you use whichever you need. Neither level is going away.
—Jens
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
