🚀 go-pugleaf

On Thu, 10 Aug 2000, Dr John Stockton wrote:

> 
> Speed is not everything; understanding and correctness are more
> important.
> 
> Where a method is defined in a recursive manner, it is better to program
> it recursively, and then to seek improvement if necessary; if the
> iterative result does not agree with the recursive, one can be sure that
> something is wrong.

Well, it is like a microsoft programmer would say... Ayway you are right,
if this code is an example in education. But if you write real programs,
speed should be important. Never forget: to write a better code should be
much more easy and effective than to develope new hardwaer just to run the
code. If you want to make a real program, never write long and slow codes
thinking that "the people who use it will buy a faster computer" because
this is not programming i think...

Anyway there aer ways to make faster te code without rewriteing, with
caches and other tricks, but i think that wouldn't solve the problem as
good as a better code would. For example virtual memory under an os: it's
nice to use only standard file handling functions and wait for the OS to
decide what to cache in memory and what not, but i think the OS knows less
about the problem than the program, so maybe if the program would choose
what should go to memory and what to a file, it would be faster. The same
about caches i think.

Anyway these are only my opinions, and i'm not a real programmer, i mean
ot with degree or something.