Linked by Eugenia Loli-Queru on Sun 5th Nov 2006 22:59 UTC
David Chisnall takes a look behind the scenes at Apple's upcoming revamp of the Objective-C language. As with any new language, some things are good, some are ugly, and some are both.
Permalink for comment 179219
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
Qt/Mac is actually a wrapper around Carbon, and unlike Cocoa and Carbon, you have to pay a four-figure sum (per developer) to build commercial applications with it.
In my own experience, there are two big problems with Qt as a platform for serious Mac applications. One is that Qt apps don't behave like normal Mac apps: for example, the menu bar is tied to the main window, and if you shut the window, the application dies. Cocoa and (normal) Carbon applications don't behave like that. It doesn't use all the Carbon widgets either, although this has improved in recent years (supporting drawers and sheets, for example).
Second, I've found that there are speed deficits. Widgets take about a second to "awaken" after you raise a Qt window on the Mac - they don't on normal Mac apps - and certain classes are sluggish, notably the text editor widget class when you write a few paragraphs with it.
Much as I love its API and I think it's fantastic on X11 and Windows, if you're looking mainly to develop Mac apps you should give Qt a miss.