🚀 go-pugleaf

KROMKAMP ANDY wrote:
> It's easy to blame it on Lazy coding, and this is at least partly true,
> but most of the problem is because of how programs are written these
> days. Mostly in C++ or C, and in groups of hundreds of people, you can't
> optimize your code the same way you can doing assembly in 64k of memory,
> because it would take forever, the task would be unbelievabley difficult.
> So you have to rely on the Compiler to do the optimizing for you, something
> which is still not a great process.

I realize that.  I'm just griping because I don't want to spend a lot of
money on RAM for my home computer when I could be buying furniture or
a deck or something for the house.  :)  Another resource hog is the visual
interfaces that programs require these days - a lot of copying bitmaps
and stuff around in memory.  To their credit, Microsoft has done a pretty 
good job minimizing the amount of virtual memory swapping that actually 
goes on.  Still, we have a joke here in the office whenever somebody reads 
about some new technology, like 1 gig SIMMS or terrabyte hard drives or 
something.  We'll always add: "...and with Windows 2000, you're going to 
need it!"