lacktheknack said:
Uhhh...
Guys?
Bricking is EXACTLY what will happen in a firmware update power cut.
Like, with ANYTHING.
The Wii U will.
A PS3 would.
My computer would.
Your phone would.
The motherboard I use in school projects will.
That's why all these things have a message saying "Do Not Turn This Device Off" during firmware updates! This isn't rocket surgery! D:<
Seriously, unless the auto-turn-off happens during firmware updates (which I bet a million bucks it doesn't), this is the biggest non-story I've seen all month.
And to everyone saying "What if there's a power outage?"
Well, what if there's an outage while the firmware of your phone/PC/other console/other electronics update? Well, you pull out your shiny warranty and get another one for the cost of shipping. Or, do what the guy above me said, and invest in an uninterruptible power supply.
Seriously, this thread consists of nothing but a bizarrely specific attempt to smear the Wii U, in a manner that is comparable to mocking the kettle for being black when the pot, the cauldron, the stove and the pans are ALSO black.
How many Firmware updates are over 5gigs? Even with a fairly decent internet connection, you're looking at at least an hour to download all that + the install time. Not to mention, the Wii-U itself is programmed to shut down if left idle DURING THE UPDATE. They basically programmed the Wii-U to commit suicide.
You can try to paint it as a smear campaign all you want, but the fact exists that there's a non-negligible number of bricked Wii-Us sitting out there because Nintendo released a giant update on day 1 for a system that, by default, will shut itself off during a long update.
Additionally, your stance is one that is paving the way for the exploitative, anti-consumer practices and poor quality that we're seeing in the gaming industry. Oh the machine doesn't work through no fault of your own? Well just pay for shipping to replace it. So a $350 console now becomes about $400 because the developer did something stupid, but we don't blame their obvious bad development choice, it's the users fault that their power/internet went down or something else went wrong - they should have been prepared for such contingencies by having a back-up generator or hard-line internet connection straight to the source instead of the machine having a fail-safe.