The who system draws 35W, the gpu is more than 5x the size of the cpu. Therefor the cpu should draw about 5 watts. Where is it written that the Wii has a ARM core for the OS? I don't think I read that from any release information unless its just rumor. 180% increase from working software is a great challenge. The software would have to be in alpha phase to consider such improvements.I guess you didnt know? The wii u cpu doesnt run the os and apps like its browser, its arm coprocessor does. You are comparing an arm to an arm, not a power derivitive.
But seriously dude, even at 24nm a subwatt processor for a battery device is NOT going to be outmuscling a walled device taking 15 watts unless there is a huge gap in time. Thats just reality man.
Like the dedicated sound chip, Nintendos system design removes all unecessary loads from the cpu.
Although 180% is nothing. Audiokinetic acheived performance increases of 500% from optimizations to their wwise 2012 v2 middleware.
developers aren't ussually ones to talk much about things like this, it took a long time before it was comon knowledge how hard it was to program for the ps3. Its not all doom and gloom since nintendo will deliver good first party games most likely and there will probably be good 360 and ps3 ports eventually.I haven't been following, but I can probably assume correctly from the last post that this thread has degraded into a bitter war over the small things.
To put it in the most basic way possible, the most BASIC way, there are developers out there who are finding the CPU underwhelming. It may or may not be the case, that this fact will affect certain game production toward the Wii U. Worst case scenario would be particular games not reaching the Wii U because of it. That's not to say that the Wii U is a flop, just that different development methods need to be adopted to make things work. Remember, that not every developer is complaining about this feature, nor are they predicting the Wii U's doom because of it alone.