4 ms·
But supporting 64-bit Carbon for their own use isn't the same as supporting it for everyone else. For one thing, only a subset of the Carbon API is important t
by makecheck 17y ago
But supporting 64-bit Carbon for their own use isn't the same as supporting it for everyone else.
For one thing, only a subset of the Carbon API is important to iTunes. And if it became necessary to fix things (or even break compatibility), they could, because the 64-bit frameworks would be private.
And it's certainly possible to port to Cocoa incrementally. It is also possible to isolate Objective-C implementations behind pure C APIs, so that an abstraction doesn't have to know it's using Cocoa on Mac and something else on Windows.
- pyre 17y agoMany of the Cocoa APIs are abstractions of C libraries like libxml, etc. But you still need to port everything that supports the Cocoa API wrapper around that C library, even if you don't have to port the C library itself.