News for hackers. Stuff that matters.
Re:Reducing runtime memory in Windows 8 by gburt on Friday October 07, 2011 @04:44PM (#3085824)
This seems largely misguided. Stuff like merging duplicate memory spots (such as that reserved for future use by applications) seems to question programmer judgment in the aim of saving available memory.

If the memory is available, you'd do better to use it, no?

Re:Reducing runtime memory in Windows 8 by singh on Friday October 07, 2011 @05:03PM (#3085938)
How is this misguided?

> If the application tries to write to the memory in future, Windows will give it a private copy

It is textbook Copy-on-write. To me it seems no judgement is made about the programmer.

>If the memory is available, you'd do better to use it, no?

I don't understand... if I have 2 GB of RAM, I should always use all of it? The case being made in the article is to minimize memory consumption to increase battery life - something that will be crucial on tablets I assume.

Re:Reducing runtime memory in Windows 8 by dorian-graph on Friday October 07, 2011 @06:27PM (#3086260)
It seems like everyone and his grandma know better than Microsoft engineers.
Re:Reducing runtime memory in Windows 8 by wmf on Friday October 07, 2011 @05:10PM (#3085974)
...question programmer judgment in the aim of saving available memory.

These are Windows programmers we're talking about. The culture doesn't seem to encourage fastidiousness.

If the memory is available, you'd do better to use it, no?

Yes, but what if you run out later? Should you do the dedupe when some other process is blocked trying to allocate memory or should you do it earlier?