Linked by Thom Holwerda on Thu 26th Jan 2012 15:13 UTC
Mac OS X "It's no longer possible to write a single app that takes advantage of the full range of Mac OS X features. Some APIs only work inside the Mac App Store. Others only work outside it. Presumably, this gap will widen as more new features are App Store-exclusive, while sandboxing places greater restrictions on what App Store apps are allowed to do." Anybody surprised by this, here's the clue stick. Please proceed to hit yourself with it.
Thread beginning with comment 504807
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 UTC in reply to "RE[2]: No MacOS X for me."
kaiwai
Member since:
2005-07-06

There are other ways of doing it, like when they dropped support for Carbon in Lion.

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.

Reply Parent Score: 2

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."
moondevil Member since:
2005-07-08

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...

Reply Parent Score: 2

RE[5]: No MacOS X for me.
by steve_s on Fri 27th Jan 2012 11:39 in reply to "RE[4]: No MacOS X for me."
steve_s Member since:
2006-01-16

Huh?

64-bit Carbon was never released. Lion is still capable of running 32-bit applications, even those using Carbon. Nothing has significantly changed about the availability of the Carbon API with Lion.

Reply Parent Score: 3

RE[5]: No MacOS X for me.
by kaiwai on Fri 27th Jan 2012 14:14 in reply to "RE[4]: No MacOS X for me."
kaiwai Member since:
2005-07-06

How is that related to the original statement you made:

There are other ways of doing it, like when they dropped support for Carbon in Lion.


They have ceased furthering its development but it is still supported as so far as receiving critical updates such as addressing security vulnerabilities.

As for the original point of deprecating API's without making them Mac AppStore only - given that there is only a single reference to a persons experience and so far all searches seem to be pointing to this one story I really question whether one is getting the full story.

Sandboxing and restrictions on the API's one can use if one sells via the AppStore - how is this surprising? one of the first things Apple said was 'no private API's to be used' then said they were going to make sandboxing mandatory (November) but later back-pedalled (now March) given that a significant number of programmers didn't have the time, resources and critical parts of the Mac OS X API were off limits of which their software relied upon to function. Even then there are exceptions one can invoke and as long as you can justify it to the AppStore curators then you're good to go.

As for iCloud - it is their service and the last thing they want are third parties screwing it up; if there are third parties going rogue they can trace if back and take corrective action. Don't think it'll happen in the future? just you wait, when Google and Microsoft's own cloud offerings before more sophisticated I can almost assure you that there will be a set of restrictions in place when accessing their services.

As I've said in the past, I know that all the 'cool kids' are beating up on Apple but lets stand back, take a deep breath, sip a cup of tea, nibble on some shortbread and chill out for a moment.

Edited 2012-01-27 14:24 UTC

Reply Parent Score: 2