@jcr: Which dead horse that I'm flogging are you referring to? I've got several. Although, unrelated, some classes and methods would make awesome horse names. I can see it now: NSArrayController SetValueForKey to win, and WebKit to place, followed by CoreImage, Objective-C Biscuit, and SetKeysTriggerChangeNotificationsForDependentKey. Bay Meadows would never be the same.
@Doc: Yeah, saying something's Cocoa if and only if it's in Cocoa.h is a cop-out. But it's a slippery slope, and as others have wisely pointed out, the distinction distracts from more important issues. A Cocoa, or mac developer should have WebKit and CoreImage as tools in their belt, but they should also know regexp, bitshifting, IconRef wrangling, and others. The horse I've been flogging has been that it shouldn't matter if something's Cocoa or not, save for the compiler needing Cocoa.h, because they should know more than just one part of an API. Specialization is for insects.
by Blain — Oct 05
@Doc: Yeah, saying something's Cocoa if and only if it's in Cocoa.h is a cop-out. But it's a slippery slope, and as others have wisely pointed out, the distinction distracts from more important issues. A Cocoa, or mac developer should have WebKit and CoreImage as tools in their belt, but they should also know regexp, bitshifting, IconRef wrangling, and others. The horse I've been flogging has been that it shouldn't matter if something's Cocoa or not, save for the compiler needing Cocoa.h, because they should know more than just one part of an API. Specialization is for insects.