3 ms·
This isn't applicable to the current situation. What Apple did with Carbon, though it was inconvenient for Adobe, didn't artificially limit Adobe. Apple simply
by chc 17y ago
This isn't applicable to the current situation. What Apple did with Carbon, though it was inconvenient for Adobe, didn't artificially limit Adobe. Apple simply didn't build in support for something that Adobe was hoping for. It's the difference between refusing to lend a friend your last $20 for a cab because you need it and putting a gun to his head and ordering him to march.
Nack said, "It’s entirely Apple’s call about what’s best for the Mac OS and how to spend their engineering cycles." Conversely, it should be entirely OUR call what's best for OUR software and how to spend OUR engineering cycles, and this is what Apple opposes. Even if we can find a way to make something work, Apple will still stop us.