There are a few others you should count in (like the Paper Mario series, and Yoshi's Story.) I tried playing Super Paper Mario Wii once, and gave up about 10 minutes or so into the game, tired of just pressing A to proceed to the next dialog line. I didn't play any of it. I would call that a miss too. It's amazing how many game designers think the player needs to be schooled for minutes on the mechanics and/or story before can start enjoying it; and even more when it's Nintendo committing the blunder with their very mascot. New Super Mario Bros goes back to the origins (once again) where you just play it.

Really? Because the only thing that I dislike is actually the multiplayer mode. Almost every interaction between the characters is meant to be disruptive. Either you stay far away from your ally, or one will accidentally end up killing the other. Maybe the fun is in obstructing the other player? Well, not for me, or anyone I invited to play with me. Good'n old Contra is much more enjoyable.

Nonsense. Wii's flash memory is 512 MB, not 512 KB. It's unthinkable for a video player to be larger than, say, 50 MB; and at that mark it would still fit.

On the NVIDIA side, CUDA performance and usage flexibility is still typically and substantially higher than is achievable via OpenCL, since obviously CUDA exists to fairly optimally exploit their GPU architectural capabilities whereas OpenCL is a generic GPU-vendor / architecture "neutral" platform that doesn't give as much card specific control as CUDA (or CAL in AMD's case).

That's not true. I've run many equivalent CUDA and OpenCL kernels on NVIDIA cards, and they perform both the same. Pretty much in accordance with those benchmarks.

There's no reason for OpenCL code to be any slower than CUDA code (the same compiler is used, only with small changes in the frontend). Maintainability on the other hand... with CUDA you can launch a kernel just like you were calling a function; with OpenCL you have almost a dozen of setup steps (reminds me of programming Win32 applications directly with raw Win32 api calls). Function and operator overloading, templates... those are nice things to have at your disposal when you need it. Let's hope they make an "OpenCL++" standard too.

Uh... no, you are wrong. Quadros and GeForces have a lot of differences in the internal hardware. Just because they "do the same thing" (they draw triangles really, really fast) it doesn't mean they are the same. GeForces, for example, don't have optimizations for drawing points and lines, nor assume you are abusing of obsolete APIs, like immediate mode drawing; both are common in CAD applications, and almost useless in games.

Are you suggesting people to use XFS? Why would you do that? That's beyond mean.

I tried migrating all my data to XFS once. About a month later I was desperately migrating it all back to ext3. Not only XFS has serious design flaws that make it one of the most fragile FS around, the driver implementation is even able to corrupt the stored data (that is, not just the directory structure, but the file contents too) even during normal operation. Two weeks after setting up a server with XFS, I had to shut it down to fix the file system errors; another 2 weeks uptime, I had to do it again, but this time only so i could back the data up and reinstall the system on an ext3 partition (same disk, not a single badblock up to this day).

Yeah, it's not like they ever delayed a Zelda game before... oh wait!

Oops, I mixed up /dev/null with /dev/zero. Never mind.

*Less* reliable? At least /dev/null willl never lose your zeros.

On a serious note, I've seen XFS fail in a machine that was rebooted normally only once; that is, installed the system on a XFS partition, booted it up, shutdown -r now after 2 months... file system error. No bad blocks on the disk, just fs corruption during normal operation.

It works, athough "ssh" will be automatically replaced by "sftp".