On Wed, Dec 10, 2008 at 7:05 AM, I. Savant <[EMAIL PROTECTED]> wrote: > On Dec 9, 2008, at 10:32 PM, Michael Ash wrote: > >> This is a common response whenever I talk about not optimizing where >> it's not useful. But the thing is, trying to optimize every little >> thing makes your app *slower*. > > ... > >> Of >> course you'll have gone through only a miniscule fraction of the bolts >> in the bridge before the people who hired you to build it get fed up >> and tell you to open it for traffic or get lost. Result: a very heavy >> bridge. > > These are two *completely* separate arguments: Development time versus > runtime efficiency.
They're not separate at all. Development time is always limited. You achieve the best runtime efficiency by focusing that development time where it can do the most good. Disregarding this by trying to optimize every piece of code in your app makes your app slower because you won't have time to do a good job on every piece of code in your app, not even close. Mike _______________________________________________ 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 [EMAIL PROTECTED]
