3 ms·
AFAICT, these aren't APIs that even Apple's own software consumes. Instead, these are the higher component-level equivalent of "private functions" in a module:
by derefr 12y ago
AFAICT, these aren't APIs that even Apple's own software consumes. Instead, these are the higher component-level equivalent of "private functions" in a module: there for the public functions to call (and for the public functions to be implemented in terms of), but not part of the contract.
Windows, to contrast, is written in such a way that you get developers finding random things (registry entries, unexported symbols, resources in random DLLs) and writing their software to depend on those being there. These are supposed to be implementation details—they're undocumented, and are supposed to be allowed to change, but—since Microsoft allows the developers of their third-party software to convert these previously-private-APIs into public APIs with API contracts, and assumes the responsibility for maintaining those APIs from then on to prevent that software breaking—it could be said that Windows doesn't really have any private APIs. (Or didn't. This is changing, first with the CLR and now moreso with Metro app sandboxing.)
OSX's public/private framework split is in large part a reaction to that, I think: Apple draws a clear boundary between "frameworks you can link against" and "frameworks we will punish you for linking against." This means that anything within the public frameworks is up for grabs—exported symbols, unexported symbols, the embedded-est of undocumented structs-in-structs-in-structs—which forces Apple to make sure that everything in them is merely flattened proxy representations, rather than something the system cares about. They're effectively following the SOA approach, with each of their public frameworks being like a service endpoint, returning self-contained resource representations rather than passing up anything from below.
- wolfgke 12y ago> Windows, to contrast, is written in such a way that you get developers finding random things (registry entries, unexported symbols, resources in random DLLs) and writing their software to depend on those being there. These are supposed to be implementation details—they're undocumented, and are supposed to be allowed to change, but—since Microsoft allows the developers of their third-party software to convert these previously-private-APIs into public APIs with API contracts, and assumes the responsibility for maintaining those APIs from then on to prevent that software breaking—it could be said that Windows doesn't really have any private APIs. So you want to morally punish Microsoft for caring more about backwards compatibility than Apple did and does (even if the developer does dubious things, such as using private APIs)?