Robert,
Many will say the X6800 is the way to go...
I will say the opposite. Their reasoning for choosing a dual vs quad core is that current applications barely take advantage of dual cores let alone quad cores.
[SOAPBOX]
IN short - This logic is flawed especially if developers are utilizing a thread pool. I will not get into what that is but essentially many developers that are creating multi threaded applications will allow the application to use ALL available resources and NOT restrict them to just TWO.
In long
,
Many of the games/applications that WILL be released will likely use as many cores as are available.
Since dual core is becoming very much the mainstream I would assume that many devs will soon be releasing software that make use of multiple cores.
PS... Very few devs in a SMP/multi core environment release code that specifically denotes which CPU/Core each part of the app should run on.
If they are, then they are very inefficient (very limited reasons to limit or direct portions of your app to run on a single proc. Like requiring full exclusive use of a resource). If people understood system context, process context, user mode and kernel mode as related to context switching they would likely revise their comments. They would also be wise to also understand the difference between user, system, interrupts and blocking, all of which happens quite efficiently at the OS/Kernel level.
Sorry about the SOAPBOX but many people here are talking down a processor as useless because it has two more cores (funny) if they only understood what was happening under the covers they would realize that the QX6700 has a LOT more to offer over the long haul.
[/SOAPBOX]