I've been watching this discussion w/great interest. Thanks.
A lot of the discussion seems to be focused on micro-optimizations and little focused on systemic optimizations.
One point that I have yet to see mentioned is the overall performance enhancements to be had by focusing on embracing the high level services of the system.
And by overall performance enhancement, I specifically mean that it lets you ship a working product in less time. And by "working product", I mean "product that performs well enough to keep customers happy".
As well, by focusing on achieving maximal integration of your code into the subsystems of the system, you can often gain a tremendous amount of efficiency.
Simple question: Is it better to pursue a 20%, or even 50%, improvement in drawing speed by rewriting in C++ or C than, say, preventing the 2, 3, 4, or more extra redraws that are happening prior to window flush? Don't laugh -- I have seen it happen. Often.
As well, there are areas of optimization for which Apple has entire teams dedicated to squeezing every last ounce of performance out of every variant of CPU and/or GPU shipped.
As an added benefit, doing so means that your code is much more likely to just get faster across major releases of Mac OS X (and a handful of minor releases, too).
b.bum _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
