Re: why use pow(x, 2)?
Re: why use pow(x, 2)?
- Subject: Re: why use pow(x, 2)?
- From: Luke the Hiesterman <email@hidden>
- Date: Mon, 2 Nov 2009 15:52:15 -0800
On Nov 2, 2009, at 3:22 PM, Bob Smith wrote:
All you youngsters who never ran an app on a CPU at less than GHz
speeds, you ought to be forced to write code for an early-80's PC.
Now that was _real_ programming!
Also simply isn't reality anymore. Period. No matter how nostalgic you
wish to be, all that matters are the circumstances of today. Since
this is cocoa-dev, I'm sure you write Objective-C these days, which is
a language wrought with function calls over the place courtesy of the
runtime. But, that's not a bad thing. We're not dying in function call
hell and more importantly, new programs are developed and brought to
users with remarkable speed. A wise man once said, the slowest program
is the one that hasn't shipped yet.
The moral of the story is that instincts on what is the best strategy
for performance are great, and shouldn't be ignored, but the only
things that really matter for performance are real numbers and user
experience. Only way to determine those things is to first build a
working version of your application. Can't do that if you're still in
the office arguing about what's the fastest way to write something
that will be done in a matter of microseconds.
Luke
_______________________________________________
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