Subject: Re: Speed is important (was Re: Why We Should Use the STL (fwd))
From: Paul Cubbage (paul@opencountry.net)
Date: Mon Jun 05 2000 - 00:21:59 CDT
I agree that speed is important to users but things that don't work but
run fast are no use. My experience is that speed originates first with
good algorithms. Having done that, the most important thing is that the
program "runs right". I don't care how fast it is if it's buggy! Ergo
I totally agree with the priorities:
> "Correctness"
> "Completeness"
> general "correctness" of an algorithm or implementation that leaves room for further optimization (for speed, size, scalability, etc.).
Once the above is achieved then optimizations can proceed for speed,
size...
If you optimize while developing you will confuse what you're
accomplishing.
There is always the condition where an early release is too large or
slow to use. Then one looks for "cheap victories" by scanning for the
obvious. I don't see that in Abi. I think reading wurd correctly will
win more users than speeding it up at this point.
After 1.0, perhaps you can apply your suggestions and work on speeding
up that release while work begins on the next.
-- Paul Cubbage, CEO 408-353-2164 408-353-8181FAX 408-472-1112cel Open Country, Inc. paul@opencountry.net 23450 Old Santa Cruz Hwy. Los Gatos, CA 95033
This archive was generated by hypermail 2b25 : Mon Jun 05 2000 - 00:18:46 CDT