Re: How Can I Notify DrawRect Method?
Re: How Can I Notify DrawRect Method?
- Subject: Re: How Can I Notify DrawRect Method?
- From: email@hidden
- Date: Wed, 10 Dec 2008 12:39:32 -0500
You both have valid points. However, I think you are missing
something. That something being the overall "goal" of the application
as predicated by that never-ever-returns: Time. That goal can be
multi-faceted. For example, one item in the overall list is "target
platform."
By deciding on what platform(s) to target, you can decide where to
spend your time during to development to achieve the results you want.
Sometimes that decision can also lead to split forks in the
development tree (e.g., platform-specific support).
Since I have found it nearly impossible to develop "the perfect app"
before writing any code or going into some sort of "demo mode," I
favor an iterative design loop: get program parameters, code, test,
check against parameters, check with client, lather, rinse, repeat.
During that design/construction cycle, one should be able to identify
what needs optimization, etc. That will cut down on the debate of
technical theory - the proof being mostly in the pudding. Of course,
the theory can help identify potential hotspots (items to watch) which
can then be checked during testing cycles.
Neither development time nor optimization are distinctly separate in
my view - they are interdependent given the goal of the application.
One may get favored over the other, but, again, that depends upon the
restrictions placed by the goal of the application.
Quoting Michael Ash <email@hidden>:
On Wed, Dec 10, 2008 at 7:05 AM, I. Savant <email@hidden> 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 (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
_______________________________________________
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