5 ms·

Why in hindsight? It was a compat layer for essentially adapting OS 8/9 software for OSX. It was deprecated in 2012. In 2017 with High Sierra they announced t

Why in hindsight? It was a compat layer for essentially adapting OS 8/9 software for OSX. It was deprecated in 2012. In 2017 with High Sierra they announced that carbon apps would require changes to work at all.

AprilArcus 7y ago
Nobody with any sense really believed Apples protestations during the 1999-2007 time period that Carbon was going to be a long term solution, but Apple really tried to sell folks on the idea that it would be, until they suddenly low-key ghosted on the Carbon developer community at WWDC 2007, when 64-bit Carbon was quietly removed from the keynote deck a year after it had been prominently featured. https://www.macrumors.com/2007/06/13/leopard-drops-carbon-64-bit-support/ https://www.macrumors.com/2007/06/13/leopard-drops-carbon-64... Archive.org records the wailing and gnashing of teeth which accompanied the relatively sudden announcement: https://web.archive.org/web/20140115143937/http://lists.apple.com/archives/carbon-dev/2007/Jun/msg00258.html https://web.archive.org/web/20140115143937/http://lists.appl... https://web.archive.org/web/20140115112428/http://lists.apple.com/archives/carbon-dev/2007/Jun/msg00292.html https://web.archive.org/web/20140115112428/http://lists.appl... You can still find developer documents in Apple's archives referring to a 64-bit upgrade path for Carbon apps. https://developer.apple.com/library/archive/documentation/Carbon/Conceptual/Carbon64BitGuide/Introduction/Introduction.html#//apple_ref/doc/uid/TP40004381 https://developer.apple.com/library/archive/documentation/Ca...
vor_ 7y ago
Apple didn't present Carbon as merely a compatibility layer at the time. It was positioned as the procedural C paradigm alongside Cocoa's and Java's object-oriented paradigms. Carbon was supposed to be one of the three development frameworks for OS X alongside Cocoa and Java, which is why Cocoa and Carbon have drink-themed names to fit with Java. Porting a classic app to Carbon was "Carbonization."

AprilArcus 7y ago

Nobody with any sense really believed Apples protestations during the 1999-2007 time period that Carbon was going to be a long term solution, but Apple really tried to sell folks on the idea that it would be, until they suddenly low-key ghosted on the Carbon developer community at WWDC 2007, when 64-bit Carbon was quietly removed from the keynote deck a year after it had been prominently featured. https://www.macrumors.com/2007/06/13/leopard-drops-carbon-64-bit-support/ https://www.macrumors.com/2007/06/13/leopard-drops-carbon-64... Archive.org records the wailing and gnashing of teeth which accompanied the relatively sudden announcement: https://web.archive.org/web/20140115143937/http://lists.apple.com/archives/carbon-dev/2007/Jun/msg00258.html https://web.archive.org/web/20140115143937/http://lists.appl... https://web.archive.org/web/20140115112428/http://lists.apple.com/archives/carbon-dev/2007/Jun/msg00292.html https://web.archive.org/web/20140115112428/http://lists.appl... You can still find developer documents in Apple's archives referring to a 64-bit upgrade path for Carbon apps. https://developer.apple.com/library/archive/documentation/Carbon/Conceptual/Carbon64BitGuide/Introduction/Introduction.html#//apple_ref/doc/uid/TP40004381 https://developer.apple.com/library/archive/documentation/Ca...

vor_ 7y ago

Apple didn't present Carbon as merely a compatibility layer at the time. It was positioned as the procedural C paradigm alongside Cocoa's and Java's object-oriented paradigms. Carbon was supposed to be one of the three development frameworks for OS X alongside Cocoa and Java, which is why Cocoa and Carbon have drink-themed names to fit with Java. Porting a classic app to Carbon was "Carbonization."