> > Maybe I'm wrong, but we have experienced enough past pivots and > bridge-burnings that another seems overdue. >
Yes, I can understand that. On the other hand, at least in the old days, Microsoft kept all the old API's around for so many years (for backwards compatibility), including bugs in the API, because people relied on them, because they had worked around them ... All of which meant that a lot of applications relied on those old API's, probably through a stack of layers, so that Microsoft could never get rid of them. Occasionally, I still see the "black movie" bug in presentations at conferences. (Meaning: the movie plays fine on the laptop screen, but on the projector, there is only a black rectangle.) So, overall, sometimes, I think, it is just necessary. A similar case is OpenGl: while it is a real PITA, i think at some point, the Khronos group had to pull the plug and design a completely new API. Best regards, Gabriel _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
