- AppKit isn't layer-backed by default, requiring you to handle this. Something as simple as setting the background color for an NSView is far more of a ritual than it is for a UIView.
- NSColor/NSImage under the hood are different than UIColor and UIImage.
- NSTableView and NSCollectionView have big differences (NSCollectionView is more subtle, I should say) that rear their head when you start trying to do anything like you would on iOS. e.g, NSTableView doesn't automatically get an NSScrollView, grouped rows operate like headers but the underlying data structure isn't easy to share, collection view items are view controllers on macOS but not on iOS, etc.
- Delegate methods are entirely different, requiring you to #if check everywhere.
- Trying to use NSTextField like a UILabel is a trip, requiring you to understand an archaic NSCell architecture that you'll wish you didn't have to deal with in 2018.
The list goes on, and most developers that share code between iOS and macOS have their own frankenstein framework floating around. UIKit on macOS would do a lot to alleviate this.
Edited because, speaking of 2018... this should not be this annoying to format.
EDIT: Looks like you got there before I finished typing.
Regardless of how correct he probably is, the fact of the matter is that there's overwhelmingly more developers on the UIKit side and that API is what people clearly prefer - the only ones voicing otherwise are old Cocoa-heads. It's ridiculous that it's 10 years later and Apple is only now confronting this.
Props to Apple for finally fixing it.
Or you just use an NSBox as the rearmost subview of the NSView, and set its fill color.
That's what a ritual is; it's 2018 and I should not have to go out of my way to set a damn background color on a view. UIView has predictable behavior, AppKit does not.
Cocoa developers tend to think it's all very apparent though. Was actually counting down until a comment like that appeared. ¯\_(ツ)_/¯