From: Gary Wright <wright_gary_r@...>
Date: 2006-03-12T02:08:42+09:00
Subject: Re: Help me understand why the Ruby block is slower than wit


On Mar 11, 2006, at 12:00 PM, Stephen Waits wrote:
> Additionally, the "no premature optimization ideal" is often taken  
> a little too far.  I intentionally call it an "ideal".  I work on  
> video games.  A good portion of our job is optimization.  If we  
> didn't do *some* premature optimization, we'd be in bad shape.

It isn't really premature optimization if you are dealing with a
known problem domain and you already have a reasonable
sense of the performance issues that you will face.  It is
nonsensical to throw away the knowledge you've gained from past
experience in the matter.

But when crafting new software, where you don't have any
particular knowledge of the performance issues, it
makes more sense to get something working correctly and in
a timely manner than to make premature assumptions about the
bottlenecks.