I don't necessarily see it as a CPU speed problem.
I see what the programmers did on the old C=64 with a
1 mhz 6502 processor and what they are doing on a 2 gig PC.
As I see it, its the programmers that have gotten LAZY.
They don't optimize their code for speed, if it works its
good enough (the processor will take care of speed).
Mel
Thats it in a nutshell. In the semester of computer science I took at University, we managed to cut down the search time from 4 minutes to 2 and a half in a database we were writing in Pascal on a B and W Mac just by optimizing our search routines and code structure.
Currently we have ludicrous situation where we need quad-core multi ghz cpu's in PC's to multitask properly.
I remember going from a 40 mHz 68030 to 40 mhz 68040 to a 50 mhz 68060 and at each step there was huge difference in performance for all tasks. Imagine, I thought, what i could do with clock speeds in the hundreds of mHZ? Now days you go from 1000 mhz to 2000 mhz and you think "Oh boot up time is the same, I can do a render/mp3 faster and...thats it"
