12 Apr
2011
12 Apr
'11
3:02 p.m.
On 4/12/11 5:55 PM, Mike Loewen wrote:
Absolutely.
<old fart>
These kids today, I just don't know..
</old fart>
-Dave
--
Dave McGuire
Port Charlotte, FL
This is
horrible. It can be avoided with some effort. I have a feeling
a lot of newbies will begin to see this as an acceptable approach,
though. Lots of people take the attitude that since memory, disk, and
CPU cycles are plentiful now, that wasting them with terrible kludges
is ok.
*shudder* I won't write software like that. I'm betting you won't either.
Some years back, I was giving a presentation to our group, explaining
why I had coded something in a particular way (because it was faster and
more efficient). One of our so-called programmers raised their hand and
asked, "Why don't you just run it on a faster processor?" I just stared
at her.
There's something to be said for learning to write code that had to fit
in 64KB (or less).