Re: ObjC in time-critical parts of the code
Re: ObjC in time-critical parts of the code
- Subject: Re: ObjC in time-critical parts of the code
- From: Dave DeLong <email@hidden>
- Date: Sun, 18 Jan 2009 17:28:51 -0700
All this reminds me a quote I found in an old PC Week:
"Objective-C is the result of adding object facilities to C with the goal of making programmers more productive. The result differs greatly from C++, which adds objects to C without making computers less efficient: quite a different goal." [PC Week, November 3, 1997]
I think bbum hit it on the head. We can get some seriously awesome optimizations out of C++, but the purpose of this languages is ultimately quite different from the purpose of Objective-C (as I see it). C++, from what I understand, is meant to be a computer efficient OO language, whereas Objective-C was designed to be a "programmer efficient" OO language.
Dave
On Sunday, January 18, 2009, at 05:19PM, "Michael Ash" <email@hidden> wrote:
>On Sun, Jan 18, 2009 at 7:10 PM, Bill Bumgarner <email@hidden> wrote:
>> 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".
>
>THANK YOU for saying this. I know that you will be attacked for saying
>this, just watch. People will say that this philosophy does not apply
>on laptops, or on iPhones, or whatever. Efficiency is always king,
>they'll say! But you're 100% right about this. "Optimization" should
>not refer to code efficiency, it should refer to *product* efficiency.
>
>Engineers treat "optimization" as a holistic process which involves
>balancing money, time, reliability, and other factors as well as
>straight-up product performance. Software engineering is no exception
>to the necessity of this, but somehow the education in this area seems
>to be completely absent. Certainly I never learned about the tradeoffs
>involved in product management when I was in school, and I don't think
>very many people do, but it's key to making a good product.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden