![]() To be fair to Apple, I doubt they made this decision lightly either. I don’t imagine the Carbon engineers were best pleased seeing a large chunk of their handiwork suddenly flushed down the drain either, but at least Apple was paying them to grin and bear it. ![]() Don’t forget that previous Leopards seeds were being shipped to Adobe and other developers with 64-bit Carbon GUI support already largely in place. The surprise itself was that June announcement, which was a total 180-degree reversal of everything Apple had said and promised up until then. I think even Apple appreciate that tossing extremely mature, reliable and optimised codebases that work without extremely good reason is not a sensible way to run a business.Īnd after killing 64-bit Carbon last June, this should have been no surprise. Not to mention the fact that they’ve been pushing developers to use Cocoa over Carbon,įor new development, sure. While you’re correct that Apple have been pushing CW users to move to Xcode for a while, this has nothing to do with what APIs you use. Xcode and CW are IDEs Carbon and Cocoa are APIs. Well to be fair, Apple has been touting XCode for the last 8 years and wasn’t shy about pushing developers to using them over CodeWarrior. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |