What is really needed is to have some of your hotshot programmers develop on 3+ year old "average" computers. Their code bloat will reduce when their own productivity suffers due to slow machines.

Still there will be cases where a lean program will run out of memory. It should do its own memory management. For instance, don't try to map in multi GB files in their entirety if you are justvstreaming data!

On Nov 4, 2012, at 6:58 AM, Charles Forsyth <charles.forsyth@gmail.com> wrote:

It needn't. Today, with the price of RAM, as many have noted, it's probably not worth the code and complexity

(though there needn't be much of either), but it can be designed and made to work well.

Also, despite the low cost of RAM, the systems still run out: my 3 Gbyte notebook running Chrome under Linux

can run out. What Linux then does with no paging file is not pleasant, so I give it a small one, and it still thrashes

trying to reclaim enough memory to continue. Pathetic.

My new 4Gb notebook has the memory soldered in (Samsung Series 9).

On 4 November 2012 14:18, hiro <23hiro@gmail.com> wrote:

that paging sucks is not a very new discovery.