AMD Zambezi news, info, fans !

[2good4you]

Then you need to take it with a grain of salt, and be skeptical of it's legitamacy, as it could be faked.
All it takes to fake that is pshopping the screen shot, putting it as the desktop and hiding icons/task bar (or just end task on Explorer).
From there, take a pic with the camera and submit to ImageShack :P

Of course it can be, or it is some kind of shot saying very little. The info plus some details seems/can be correct.
Like aero, and aero effect at the pointer and closingicon is lightening etc.

My reading seems to have led us to believe they will show up as two threads per core, but that would mean an 8 core = 16 threads.
I don't see AMD going about it that way, so I might be understanding it slightly wrong, and it is 1 core = 1 thread, but each core processes as if it was two threads due to the split architecture.
Still, I'm 98% sure ONE module = TWO physical cores, which is why an E350 Bobcat is dual core and only uses one module

I did not wrote that and has never done.
2 integer execution-cores per module=2 threads per module, and the floating point unit can execute 4x256-bit instructions in one cycle or 8x128-bit instructions in one cycle.
I have wrote AMD's latest official statement, and also my own opinion of the design, which cover a lot more than the execution-logic.

If it turns out an 8-threaded Intel performs as well as an 8core AMD, then what are we left to say? :\

It will not.

Your best bet would be Valencia for desktop, as it'd be cheaper since you'd only be going with a C32 board instead of G34.
It'd only be a max of 8 cores still, but hopefully the memory performance and HyperTransport can make up for that a bit
If you've got the cash though, I suppose you could liken the 12/16core Interlagos like the Extreme i7 chips, and G34 to the x58 since the costs will be close.

It's still up to AMD to launch a primary server part cpu for desktop use.

Again, I'm pretty sure it's 2 physical cores, sharing only the 64KB of L1 Instruction and 2MB of L2 cache per module.
The L3 is shared amongst the whole CPU, same as it has been so far.

And still as I have stated, they share _all_ units in the module except the L1 datacache. The fetch, branchpredictor and all the schedulers are all shared.
Some details are for sure still unclear. Bulldozer will (must) have a extremely powerful front end to decode and schedule for two integer execution cores.
It also have dedicated scheduler for floating point operations which seems good. Bulldozer will because of this statement shine in singlethreaded applications.