wraggster
February 13th, 2007, 21:13
The Pensive Gamer (http://blogs.spouting-tech.com/thepensivegamer/2007/02/here_comes_home_1.html) have done a great article loooking at homebrew on the Wii and the future of it:
Of all the current generation console makers, Nintendo appears to be the most reluctant when it comes to legitimate homebrew. They currently do not have an official strategy unlike Sony and Microsoft. While they said games by independent developers will happen fairly soon through a new Games Channel, I would guess 'independent developers' doesn't mean 'amateur/homebrew developers'. I'm sure we will find out at this year's GDC.
While Nintendo may not have an official homebrew strategy, the Wii appears to be the first of the current generation consoles to be hacked (no soldering required) to support homebrew applications and emulators. However, the only avenue suitable for mass market homebrew is the optional download of the Opera 9 web browser. The browser is currently a free beta but will apparently cost $5 dollars a few months after its official release.
The Web Browser
Nintendo's choice of Opera makes a lot of sense. Opera is feature rich and is available for numerous platforms including mobile phones and even the Nintendo DS. What is curious is the need to download it. Why not include it in the Wii, particularly when a less feature rich version of the Opera 9 browser is included and used by the Shopping Channel?
Perhaps it was the need to pay royalties or the fact it was going to take more time to perfect. Regardless, a downloadable browser that supports JavaScript, CSS and Flash (up to version 7) certainly provides a wealth of possibilities, like the PS3. Unlike the PS3 there is more talk of people doing web-based Wii homebrew. There are sites tracking usable Flash games, people figuring out how controller input gets mapped to JavaScript and Flash, and even media centers.
We are talking about web applications so many, if not all, of these applications and games will work on the PS3. However, people are building the sites and applications because of the Wii and as I mentioned in the PS3 article, you can build experiences sðecific to the console using user agent detection. Perhaps that is what WiiAim will do.
Console detection is important since there is a big discrepancy in the screen resolution offered by the Wii, which is primarily designed for standard definition television, and the PS3, which is primarily designed for high definition television. So if you are looking to build web sites or applications specifically for the Wii this design guide may be of help.
If there is anything to be concerned with, and this applies to any console based web browser, it's security. All web browsers have security holes, it is just a matter of finding them. Given the Wii's web browser is Opera 9 it has a high chance of having Opera 9 security holes.
In fact a vulnerability was already found early this year. The vulnerability can cause the Wii to crash requiring a power on/off to fix the problem. This may point to a weak or non-existent sandbox around the browser, which in turn could mean the potential to either brick the Wii or have the Wii run unintended code upon visiting a malicious web page.
This isn't scare mongering, the Wii just happens to be the first of the current generation consoles to have such a vulnerability revealed. Of course, I don't expect too many people to do their online banking via their Wii.
In general, seeing console vulnerabilities isn't much of a surprise. Traditionally consoles were closed gaming systems but today all the consoles are online and getting features that blur the line with a traditional computer. Hopefully all three console makers have done adequate vulnerability assessments of their system software and will patch adequately.
Bottom-line: In the PS3 article I mentioned web-based console homebrew being a wild card with potential. It is the Wii that is leading this charge. I doubt Nintendo will officially support it, but Wii owners are definitely making a mark. While security issues may eventually be a concern, the big thing that may stand in the way is that the web browser must be downloaded and will eventually have a small fee.
Of all the current generation console makers, Nintendo appears to be the most reluctant when it comes to legitimate homebrew. They currently do not have an official strategy unlike Sony and Microsoft. While they said games by independent developers will happen fairly soon through a new Games Channel, I would guess 'independent developers' doesn't mean 'amateur/homebrew developers'. I'm sure we will find out at this year's GDC.
While Nintendo may not have an official homebrew strategy, the Wii appears to be the first of the current generation consoles to be hacked (no soldering required) to support homebrew applications and emulators. However, the only avenue suitable for mass market homebrew is the optional download of the Opera 9 web browser. The browser is currently a free beta but will apparently cost $5 dollars a few months after its official release.
The Web Browser
Nintendo's choice of Opera makes a lot of sense. Opera is feature rich and is available for numerous platforms including mobile phones and even the Nintendo DS. What is curious is the need to download it. Why not include it in the Wii, particularly when a less feature rich version of the Opera 9 browser is included and used by the Shopping Channel?
Perhaps it was the need to pay royalties or the fact it was going to take more time to perfect. Regardless, a downloadable browser that supports JavaScript, CSS and Flash (up to version 7) certainly provides a wealth of possibilities, like the PS3. Unlike the PS3 there is more talk of people doing web-based Wii homebrew. There are sites tracking usable Flash games, people figuring out how controller input gets mapped to JavaScript and Flash, and even media centers.
We are talking about web applications so many, if not all, of these applications and games will work on the PS3. However, people are building the sites and applications because of the Wii and as I mentioned in the PS3 article, you can build experiences sðecific to the console using user agent detection. Perhaps that is what WiiAim will do.
Console detection is important since there is a big discrepancy in the screen resolution offered by the Wii, which is primarily designed for standard definition television, and the PS3, which is primarily designed for high definition television. So if you are looking to build web sites or applications specifically for the Wii this design guide may be of help.
If there is anything to be concerned with, and this applies to any console based web browser, it's security. All web browsers have security holes, it is just a matter of finding them. Given the Wii's web browser is Opera 9 it has a high chance of having Opera 9 security holes.
In fact a vulnerability was already found early this year. The vulnerability can cause the Wii to crash requiring a power on/off to fix the problem. This may point to a weak or non-existent sandbox around the browser, which in turn could mean the potential to either brick the Wii or have the Wii run unintended code upon visiting a malicious web page.
This isn't scare mongering, the Wii just happens to be the first of the current generation consoles to have such a vulnerability revealed. Of course, I don't expect too many people to do their online banking via their Wii.
In general, seeing console vulnerabilities isn't much of a surprise. Traditionally consoles were closed gaming systems but today all the consoles are online and getting features that blur the line with a traditional computer. Hopefully all three console makers have done adequate vulnerability assessments of their system software and will patch adequately.
Bottom-line: In the PS3 article I mentioned web-based console homebrew being a wild card with potential. It is the Wii that is leading this charge. I doubt Nintendo will officially support it, but Wii owners are definitely making a mark. While security issues may eventually be a concern, the big thing that may stand in the way is that the web browser must be downloaded and will eventually have a small fee.