Linked by Thom Holwerda on Thu 27th Dec 2012 19:50 UTC
Permalink for comment 546540
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
More News »
Sponsored Links



Member since:
2011-05-19
That's true, but again, it's still not the whole story.
There's an MSO.DLL and an MSORES.DLL that collectively take up 210 MB of RAM. But these are loaded once -- even if you load all the Office programs simultaneously.
And even then, it doesn't actually take up 210 MB of physical memory. Remember that Windows NT has a demand-paged virtual memory system. Those files are demand-paged into memory, 4 KB at a time. Until one of the Office programs actually calls a function located on a certain page, then that page is not actually taking up any RAM.
The Excel icon now takes 173 KB of disk space. One icon. (At 256x256, 32-bit color, as a high-quality PNG.) Now think about how many other icons there are in Office.
And not just icons. Fonts. The new equation editor. A new ligatures-aware layout engine. New PivotTables. More accurate statistics functions (the old ones are still there, to get bug-for-bug backward compatibility).
One man's bloat is another man's feature. You may not use a given feature, but other people do.