> Cocoa (like everything) has some rough patches, but overall is clean, elegant, and has a pretty consistent feel and vision.
Exactly. Also, Apple has the courage to regularly deprecate and subsequently remove things from Cocoa/Core/Darwin, keeping it clean, focused and elegant.
Which bring us to the GGP comment:
> But any other API that is capable of as much as Win32 is would end up looking almost as bad, minus a lot of the legacy cruft, except of course in the time it takes to develop such an all encompassing API, you'd end up with legacy cruft all of your own!*
To which I disagree wholeheartedly (not just because of Cocoa, but every single sane API out there regularly deprecates then drops stuff). Win32 accreted features around a core of cruft like a black hole. The only solution for Microsoft is to relegate the 8/16/32bit heritage lying at its core and drop it dead as it's collapsing under its own weight. Which is what they did with the Win8 internal design, where Win32 is relegated to a gangrenous limb awaiting to be severed.
Exactly. Also, Apple has the courage to regularly deprecate and subsequently remove things from Cocoa/Core/Darwin, keeping it clean, focused and elegant.
Which bring us to the GGP comment:
> But any other API that is capable of as much as Win32 is would end up looking almost as bad, minus a lot of the legacy cruft, except of course in the time it takes to develop such an all encompassing API, you'd end up with legacy cruft all of your own!*
To which I disagree wholeheartedly (not just because of Cocoa, but every single sane API out there regularly deprecates then drops stuff). Win32 accreted features around a core of cruft like a black hole. The only solution for Microsoft is to relegate the 8/16/32bit heritage lying at its core and drop it dead as it's collapsing under its own weight. Which is what they did with the Win8 internal design, where Win32 is relegated to a gangrenous limb awaiting to be severed.