I think Apple is making mistake by not featuring any development in
Carbon.
That part I agree with - it's throwing a wrench in the gears of many
developers who were following Apple's own advice to update their code
to the brand-spanking new HIObject hierarchy to make their apps future
proof. That was one wasted year between WWDC 06 "here's how to build
your app with 64bit Carbon" and WWDC 07 "what Carbon?".
If developer wants to develop application for multiple
platform, he has to use Carbon
No. For example, both Qt and wxWidgets are working on Cocoa
implementations of their cross-platform frameworks. And quite frankly,
after going through the OS 9->OS X->Xcode->Intel transitions and
facing the port to Cocoa right now, I'm very happy about every single
line of code that used wxWidgets instead of a native call. My personal
advice would be that if you want to be independent of Apple's
decisions, don't use their frameworks. There are alternatives.
Carbon
is truly a great language which does not bind itself to any language
strictly while cocoa extensively binds itself to obj-c.
Xcode 3 ships with built-in templates for Ruby/Cocoa and Python/Cocoa
applications. Granted, working mostly in C++ this is not the most
convenient way of doing things for me, but NSString is not any more
laborious than CFString. If you are smart enough to understand FSRefs
and HFSUniStr255, Cocoa will be easy. Just don't let the square
brackets scare you.
-Stefan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
