From: Tim J. <tj...@to...> - 2007-06-18 16:16:27
|
On Jun 18, 2007, at 1:12 AM, Kristoffer Lawson wrote: > On 18 Jun 2007, at 07:04, Kevin Walzer wrote: > >> Let's set aside the issue of the major commercial Mac software >> vendors, >> such as Microsoft and Adobe, and the fact that their major >> applications >> are all Carbon. Has Apple given any consideration to the fact that >> nearly every cross-platform GUI toolkit uses Carbon for its windowing >> system API? Not just Tk, but Qt, wxWidgets, and RealBasic, for >> starters. >> Or perhaps they have given this thought, and want to discourage >> cross-platform toolkits? > > But why do they use Carbon? Why not move to Cocoa in their cases as > well? Objectionable C - that's why. We old-timers know C and C++, and Carbon works with C and C++. To make the move to Cocoa, we need to move our knowledge base to Objective C. While that may be a simple thing for new programmers, for us old dogs, it would be a dramatic new trick. Additionally, it means developing an entire new code base for existing applications. > I can understand the move from Apple's point of view perfectly. > In fact, it has been a public secret for years that Carbon will be > deprecated at some point and that developers should use Cocoa. It's a > lot of work to maintain to APIs and does not make much sense for > Apple. But, they set the precedence... > I can't really see the benefit in holding on tight to Carbon. > Besides, purely from a user's perspective, Cocoa application in > general feel more refined. > > / http://www.fishpool.com/~setok/ They feel more refined because the developers didn't take the time to make things correctly in the Carbon version. There are a lot of Carbon-based apps out there that have a feel and workflow as refined as any Carbon app. Tim |