Well I'm not writing to the cocoa API. I don't have time for this API
shuffling that Apple does. I'm seriously considering rewriting my app using
C# and the Microsoft APIs (which are being ported to the Mac).
On 6/15/07 9:08 PM, "Laurence Harris" <email@hidden> wrote:
> On Jun 15, 2007, at 8:20 PM, Tony Scaminaci wrote:
>> My opinion for what it's worth is that Apple would like Carbon to
>> go away if possible.
> Old news. Apples been pushing developers toward Cocoa since the
> beginning. It's only been more recently that they've been crippling
> Carbon to provide more motivation to make the switch.
>> The fact that Carbon is still around means that many developers
>> don't want to start all over again in Cocoa and for those cross-
>> platform applications, which is the easier to maintain, Carbon or
>> Cocoa? I think Carbon survived long beyond the transition to OS X
>> because there were too many applications already written with that
>> API and developers don't want to redo all their work just because
>> Apple has decided Cocoa is the new API dujour.
> Carbon stuck around because Apple felt they needed the Carbon
> products they'd have lost without it. Apparently now they feel they
> can afford to lose a few products so they're getting more serious
> about reducing the resources invested in maintaining Carbon.
>> It's difficult for any company to justify maintaining two competing
>> platforms. Apple clearly prefers Cocoa as an API and a platform and
>> I'm sure it's costing a pretty penny to keep Carbon alive. If I
>> were Apple, I wouldn't want to do this because it doesn't make
>> economic sense. But Apple is finding itself in a bad position
>> because developers are fighting against Apple's platform of choice.
> Not fighting, just not embracing. ;-)
>> The only reason Carbon is still viable is because Apple doesn't
>> want to alienate developers.
> Or at least, they didn't.
>> However, if they slowly eliminate some desirable features, it's
>> possible that developers will eventually migrate to Cocoa out of
>> sheer frustration.
> Or stop developing for the Mac. I hope Apple isn't under the
> misconception that people don't have options here. If you can make
> the switch to Cocoa development you can make a switch to another line
> of work completely.
>> If you can't force them to switch, then make life miserable to the
>> point they decide to switch on their own. I think that's where
>> we're headed...
> Do not post admin requests to the list. They will be ignored.
> Carbon-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> This email sent to email@hidden
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden