Linked by Thom Holwerda on Thu 26th Jan 2012 15:13 UTC
Thread beginning with comment 504727
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[3]: No MacOS X for me.
by kaiwai on Fri 27th Jan 2012 02:06
in reply to "RE[2]: No MacOS X for me."
There are other ways of doing it, like when they dropped support for Carbon in Lion.
No need to have certain APIs AppStore only.
No need to have certain APIs AppStore only.
When did they drop support for Carbon in Lion? last time I checked Microsoft Office 2011 was still a predominantly a Carbon application along with Adobe's Creative Suite too.
RE[4]: No MacOS X for me.
by moondevil on Fri 27th Jan 2012 10:40
in reply to "RE[3]: No MacOS X for me."
Actually it is so since Leopard that Cocoa APIs are only partially available in 64bit.
http://developer.apple.com/library/mac/#documentation/Darwin/Concep...
Some Carbon Managers and technologies are significantly reduced or unavailable in 64-bit applications...





Member since:
2005-07-08
That's not the point of the change. The point is that they want control over the APIs that are being used. They want to be able to deprecate Carbon and UNIX APIs in favor of Cocoa. They want people to use ONLY the new APIs that are 99% share-able with iOS and that are not difficult to maintain in the following years.
"
There are other ways of doing it, like when they dropped support for Carbon in Lion.
No need to have certain APIs AppStore only.