|
You see, being a geek I know the difference.
The best example of "WHY THE HELL IS THAT WASTING MEMORY" is Excel 97. When you loaded the spreadsheet, you also loaded a mildly amusing flight simulator. If I recall correctly, highlighting X:23 through L:23 and hitting the graph icon invoked it. There was no disk activity, so it was resident in memory all along. It allowed you to fly through a blue/purple landscape and at the center was a pillar with a scrolling marquee of credits. No wonder Microsoft products are so slow.
A twenty-something year old game called "Quest for Camelot" is another good example. With functional code, it would have loaded and run fairly quickly. Ah, but ah. It had to account for perverts. While playing it (with my wife), I instructed Arthur to "fuck Guenevere". Her response was, "There will be plenty of time for that when you return, dear." So I instructed him "Fuck horse." Guenevere responded, "Those are not the thoughts of a pure man." Now in the instructions at the beginning of the game, it said you could only win if you were pure of heart and mind. My wife yelled, "If we loose this game because of that I'm going to be really pissed!!!!"
So, how many lines of code? Probably on the order of a million necessary, rather than gratuitous. The library routines don't count. In reality? Check out what Congress just passed and you'll be closer to the mark.
|