From: Jason Roelofs <jameskilton@...>
Date: 2010-05-14T10:18:33+09:00
Subject: Re: ease of porting (translating) ruby to C (vs. python)?

--00c09f905eed3ed476048683a7d1
Content-Type: text/plain; charset=ISO-8859-1

On Thu, May 13, 2010 at 9:07 PM, Colin Bartlett <colinb2r@googlemail.com>wrote:

> On Thu, May 13, 2010 at 11:11 PM, Caleb Clausen <vikkous@gmail.com> wrote:
> > While one should not get overwrought about performance ahead of time,
> > it is something that should be considered at design time. I am not a
> > subscriber to the notion that many seem to promote that performance
> > should not be considered at all until you prove with benchmarks that
> > something is too slow. I don't need to run a bubble-sort to know that
> > it's slow.
> Seconded!
> Some time in the 1920s a famous British aeronautical engineer/theorist
> (so famous I can't remember his name!) gave a lecture pointing out
> that whilst individual parts of an aeroplane gave rise to perhaps an
> extra 3% to 5% drag, the overall effect of the sub-optimal design of
> the parts was a serious increase in drag over what it could be reduced
> to. (I made the numbers up, but the gist is true.)
>
>
Which kind of brings this full circle:

Good design will always beat the pants off of hasty premature optimization,
no matter what language you use, and is an important lesson the guy the OP
is dealing with has yet to learn.

Jason

--00c09f905eed3ed476048683a7d1--