>>>A very readable foray into code size optimization, even if you're not a Linux/assembler guru:
>>>
>>>http://www.muppetlabs.com/~breadbox/software/tiny/teensy.html
>>
>>Interesting stuff. And it's good to see you are still in touch with your inner gearhead ;-)
>>
>>I do question how important it is any more in most applications to bum code down that relentlessly. Process control code or loops that execute bazillions of times, sure. But for a typical business app what difference does it make how big the EXE is? When terabyte drives go for a song that has fallen off my radar. Am I mistaken?
>
>Well, with typical business apps, you can just look in Task Manager at memory and CPU utilization. As long as memory in use is less than the amount physically installed, it makes no difference. And for CPU, most business workstations are rarely over 5% utilization.
>
>I thought another interesting aspect of the article was the idea that "every single byte in this executable file can be accounted for and justified". That's important in security research, amongst other things.

Maybe my aims are too low. I honestly believe that is no longer possible.

Possibly a non sequitir but I remember when I used to know what practically every file on my hard drive was there for. There were probably a few thousand of them in total and they all installed into their own directories. Those days are long gone, aren't they?