Linked by Thom Holwerda on Thu 14th Jun 2007 15:58 UTC, submitted by Jeremy Fox
Carbon will not be 64bit in Leopard. "At last year's keynote, Apple had claimed that both Carbon and Cocoa would be 64-bit, adding to the 64-bit fundamentals that Tiger had laid. However, according to the latest on Apple's website, Leopard's 64-bit frameworks will include the POSIX and math libraries found in Tiger, Cocoa, Quartz, OpenGL, and X11 GUI framework. In addition, Apple confirms that Carbon will not be 64-bit on the Carbon Developer mailing list." In addition, the readme file included with Leopard's developer preview says G3 support will be dropped from Leopard.
Thread beginning with comment 248201
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Vista? (bye bye rating points)
by ThanhLy on Fri 15th Jun 2007 21:07
in reply to "RE[6]: Vista? (bye bye rating points)"
Member since:2006-03-14
While for the OSX case it is different (I think), the Cocoa is the API for the OSX and Carbon was the API for MacOS. So Carbon is still supported to enable one to run old MacOS apps. So the developers for OSX chose Cocoa, the native API here.
That's not quite the way it works. You can't take pre-OSX binaries and run it natively, that's what the infamous "Classic Mode" was for. Carbon is about bringing the classic API into OSX to make it easier to *port* old Mac apps. So that companies like Adobe won't abandon the Mac platform altogether.
BTW, .Net is not a virtual machine. It really is a development platform. The intermediate byte code is compiled into native code and stored in a "warehouse" so it only has to be done once.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2007-04-06
What is the native API for XP? I was under the impression that the native API for XP is Win32 while the .Net is more like a virtual machine similar to the one used for Java. So the developers stuck to the native API (Win32).
While for the OSX case it is different (I think), the Cocoa is the API for the OSX and Carbon was the API for MacOS. So Carbon is still supported to enable one to run old MacOS apps. So the developers for OSX chose Cocoa, the native API here.