Considering the fact that the PS4 is probably going to be insanely expensive to make with the specs it has, it probably won't even be in the same price range as the Wii U, unless Sony wants to sell the system at a loss so big that they may as well blow their heads off with a shotgun while they're at it.

Nintendo needs to stop living in their fantasy world and accept that a large number of people have more online friends than real life friends, often only having access to the online variety.

We know that the CPU has Watson-like architecture, so that should be pretty great once developers begin to unlock it, and it combination with the GPGPU, the GPGPU should be able to handle some physics of its own, creating perfect gameplay mechanics...like I said, once developers unlock it...

~~~~~

RAM, 2 GB, 4 GBit chips (512 MB), @ 12.8 GB/s, with 1 Gb for OS, and 1 GB for Games (CPU, GPU)

GPGPU: Customized Radeon HD e6760 (AMD confirmed this to me in an email, actual specs customized by Nintendo) however the base specs include 480 stream shader processors, and DirectX 11 capabilities (which would me amazing detail levels even though it can't be used on a Non-Microsoft system, i.e. PC, Xbox) 550 MHz is pretty good I guess.

CPU: 3 Customized PowerPC 750 cores clocked @ 1.24 GHz. IBM has obviously upgraded the cores so yeah.

EDIT: About 4x more powerful than PS360

First off, GPGPU is not a piece of hardware; it's a name given to the act of running code traditionally meant for the CPU on a GPU. Second, Havok already confirmed that their physics engine included in the Wii U dev kit will be running on the CPU and not the GPU, presumably because advanced GPU-accelerated physics would suck too much performance away from the GPU and not leave enough resources left to produce graphics that can compete with or surpass current generation systems. And third, Wii U will be using OpenGL instead of DirectX, like all non-Microsoft hardware/operating systems, which can still handle most of the technologies that DirectX can, such as tessellation.

CPU-wise, I believe the Wii U will probably tie with current gen. The IPC (Instructions Per Clock) of the Wii U's CPU will undoubtedly be much higher than the 360's CPU do to it being a more efficient architecture, which means it'll be able to deliver comparable performance even with its lower clock speed. The fact that it supports Out-of-Order Execution also makes up for its lack of Hyper-Threading, since it can juggle tasks between its supposed three physical cores with ease; something the 360 can't do, which is why it needs its six threads to handle heavy workloads. Essentially, it delivers about the same performance in a much more efficient package.

When it comes to GPU and RAM, that's where the Wii U will probably shine the most. We hardly know anything about the GPU, but one of the few things we know for a fact is that the system has 2 Gigabytes of RAM to work with, half of which will be available to developers. That's at least DOUBLE the amount the 360 has to work with, and it's possible that more RAM will be freed up for developers to use as the system matures. It's hard to believe the Wii U actually requires a whole Gigabyte to handle whatever it's doing behind the scenes, so it might be a placeholder amount until Nintendo solidifies their ideas for the system.

Exactly what we've been saying then. Shame it won't shut up the haters, since they'll cling on to false information for dear life because they can't handle being proven wrong.

Well about the GPGPU, I've personally asked AMD before via email, and they confirmed to me that it was a customized e6760.

I think a 6760 would be way too new and expensive for Nintendo to consider using it. Plus, I think most rumors have pointed it out as being based on the R700 series, which would be the Radeon HD 4000 series.

Odd...it's possible that GPU-accelerated physics wouldn't leave enough processing power for the GPU to handle Xbox 360/PS3 level graphics, but who knows. While the Wii U's GPU is undeniably more powerful, it's highly likely that it can't handle such a massive task while maintaining that status.

I'd love to see what developers could due with the Havok physics engine by having it run on the GPU, since the engine has been demoed in the past using OpenCL.

All the bad news is a bit disheartening, but it's about what I expected. Lower clockspeed = harder to directly port games without having to rebuild the framework of the game from the ground up. We know for a fact that the Wii U's CPU is better than the 360's in certain areas, mainly with its support for out-of-order execution, but most developers are so heavily invested in current generation hardware that it's a tall order to suddenly add a completely different architecture into the mix. When it comes to cross-platform titles, we probably won't see good Wii U ports until next generation consoles from Sony and Microsoft come out with similar enhancements and developers are forced to embrace the new technology.

I couldn't get one due to money issues. I DID get hired for a position as a clerk for an upcoming Save-A-Lot that's about to replace a Giant Eagle that went out of business a years or so ago. Surprisingly, this was the very first job application I ever sent out, so I think I got off ridiculously easy compared to a lot of people. I should have enough money to get a Wii U and an HDTV to replace my crappy tube TV from the 90s after a month of work.

Keep in mind this is coming from a team that can't optimize their games to save their lives. Just look at how terrible Metro 2033, a game released in 2009, runs on even the highest-end GPUs released in 2012.