>An App Store isn't that great for developers ... when it's the only option available. That is not the case with the Mac App Store.
I keep hearing this, but I've yet to be convinced.
Over the last 5-10 years Apple has pushed developers more and more aggressively. They put giant efforts into things like Classic and Rosetta, only to strip them from the OS entirely a few years later. They repeatedly trumpeted the full equivalence of Carbon and Java to Cocoa, and now it's infeasible to use either as the basis for any full-featured application. They developed all kinds of new APIs for QuickTime in 10.5, and then in 10.6 introduced "QuickTime X" as the only 64-bit native solution, effectively deprecating everything else. And most recently there's this unusual attack on the Flash plugin of all things. It's as if they now revel in actively destroying backwards-compatibility.
All of these decisions had the effect of reducing Apple's support and maintenance overhead while strengthening their control over the direction of their platform.
I would be surprised if Apple's very clearly demonstrated zeal for taking control and eliminating developer options did not extend to the new Mac App store.
Seems to me that putting giant efforts into things like Classic and Rosetta prolonged the ability for developers to move over before dropping legacy support. The other options would be:
a) support the legacy systems forever.
b) don't support them at all.
Option A leads to a Windows-esque environment where support for older platforms actively holds back development and innovation for newer ones. Option B kills everyone's existing apps. Neither of those sounds like a very developer-friendly or even user-friendly option.
Frankly, the fact that they built those at all shows that they're willing to go the extra mile to make sure that their developers have the heads up to upgrade their applications before breaking them entirely.
Developers are mostly irrelevant in this calculus to Apple: it's what the user sees that matters. They put out Classic and Rosetta not to help developers — they were with both very clear: the train is pulling out of the station, you'd better get on board with the new thing immediately or you're dead — but to help users have something to run on the new systems. Get users buying new systems, developers will follow... especially when essentially forced to.
It seems to me that you've started with a conclusion and found facts that fit your thesis. That's the wrong way to go about reasoning.
The known facts about the Mac App Store are that it is only going to be an additional way to obtain software. It doesn't make sense to condemn it as "Bad For Developers" based on groundless speculation and presumed irrationality on Apple's part.
>It seems to me that you've started with a conclusion and found facts that fit your thesis. That's the wrong way to go about reasoning.
So let's look at it logically then. In nearly every example I gave, did or did Apple not make a promise to developers which it then broke later, costing those developers time and revenue?
And did or did Apple not recently make a promise to developers regarding the availability of an existing, long-standing technological alternative, that being direct downloads of application binaries?
Would a reasonable person extrapolate from those past observations that Apple would behave in a similar manner when circumstances similar to those that I mentioned arose?
If not, then either you don't believe that people's future actions have anything to do with their past actions, or you disagree with a series of easily verifiable facts.
there is a cost to maintaining features - ten years ago making java a first class desktop citizen was a good thing. today circumstances have changed and it's not worth the effort. so you could say that they have broken a promise - but do you expect that promise to be for evermore? or for as long as is reasonable (for some definition of reasonable)?
apple has always been that way, making life harder for developers if it suits what they perceive the consumer's needs to be.
> All of these decisions had the effect of reducing Apple's support and maintenance overhead while strengthening their control over the direction of their platform.
Yup, plus the effect of improving user experience.
The most developer-friendly thing a platform vendor can do is attract users. Apple's done that in spades.
I keep hearing this, but I've yet to be convinced.
Over the last 5-10 years Apple has pushed developers more and more aggressively. They put giant efforts into things like Classic and Rosetta, only to strip them from the OS entirely a few years later. They repeatedly trumpeted the full equivalence of Carbon and Java to Cocoa, and now it's infeasible to use either as the basis for any full-featured application. They developed all kinds of new APIs for QuickTime in 10.5, and then in 10.6 introduced "QuickTime X" as the only 64-bit native solution, effectively deprecating everything else. And most recently there's this unusual attack on the Flash plugin of all things. It's as if they now revel in actively destroying backwards-compatibility.
All of these decisions had the effect of reducing Apple's support and maintenance overhead while strengthening their control over the direction of their platform.
I would be surprised if Apple's very clearly demonstrated zeal for taking control and eliminating developer options did not extend to the new Mac App store.