<font color=blue>I think that you can do a heck of a lot more with them today.</font color=blue>
No argument there, Buck. My point is that for most of our needs, we don't need any more horsepower than has been available for years now. I can surf the net, process words, create and run spreadsheets and manipulate photographic images in a matter of seconds. Even when I'm compiling software I'm barely able to sip my soda before it's done (I'm not part of corporate-sized projects any more, so I don't have multi-million line source code).
If you are heavy into hi-res graphics, video production, 3D rendering or just like to play video games, then of course you can
never have too much speed and power.
<font color=blue>tremendous improvements in compiler an debugging tools</font color=blue>
No argument there, either. But don't fool yourself into thinking the resultant executable code is more efficient than it used to be. These tools are more for improving programmer productivity than they are for reducing the size and execution time of the final product. I wrote a complete TECO editor and a 6502 assembler (not dating myself
too much, am I?
), and they each ran in less than 4K of memory. Not bragging here, but although you could write the same thing faster in C++, using OOPS classes, there is no way it would be smaller or faster.
<font color=blue>used to love spending all day optimizing code. Today I don't have to. There is no need. </font color=blue>
And that will continue to be the case as long as computers keep getting bigger, faster and more powerful. Some of us just can't afford the upgrades.
I'm not as argumentative as I sound, Buck, but I'm
full of opinions. /w3tcompact/icons/laugh.gif