I'll be the contrarian and suggest if they are editing books and such as a job that gobs of memory might be warranted. There was a reason years ago desktop publishing required a mac and a high end machine.
It will really depend on what software is being used and what size documents they are manipulating. Do these books have embedded graphics? Are they loading the book or just chapters one @ a time. Has anyone ever used a program with 300 pages of formatted text and 75 embedded graphics?
I only mention this because casually dismissing it as a task best suited for a 'regular desktop PC' might be doing them a disservice; I have a 8Gb Latitude with an i5 and it is woefully inadequate for what I need to do @ work (probably because of SEP); I don't manage large documents.
It sucks having a poor tool to work with 8 hrs a day.
All CPUs are multi core so no escaping that. I would spend my ka-ching on memory.
It will really depend on what software is being used and what size documents they are manipulating. Do these books have embedded graphics? Are they loading the book or just chapters one @ a time. Has anyone ever used a program with 300 pages of formatted text and 75 embedded graphics?
I only mention this because casually dismissing it as a task best suited for a 'regular desktop PC' might be doing them a disservice; I have a 8Gb Latitude with an i5 and it is woefully inadequate for what I need to do @ work (probably because of SEP); I don't manage large documents.
It sucks having a poor tool to work with 8 hrs a day.
All CPUs are multi core so no escaping that. I would spend my ka-ching on memory.
Last edited: