They did make efforts to hide the browser and I assume they were constrained by the need to enable users to access captive portals. A random Ruby interpreter by some developer not part of Nintendo is not in any way necessary for them, so there's no reason for them not to take the game down. Which they did. The reason why should be obvious.
As for their efforts: They've made far more effort than they ever have before. Using homebrew or custom firmware effectively means you can't ever use that device online again (which wasn't the case for earlier consoles).
Are you suggesting that just because they've made mistakes that they would be in any way inclined to let the Ruby thing go?
> Are you suggesting that just because they've made mistakes that they would be in any way inclined to let the Ruby thing go?
I didn't mean to suggest that! Sneaking a Ruby interpreter into a game without telling Nintendo was stupid, and Nintendo's response was entirely logical and acceptable.
However, if Nintendo had known about the Ruby interpreter and had reviewed it beforehand, but denied it anyway... well, I still wouldn't find that particularly scandalous, but I would say it's a bit of a dumb precaution on a device with a Javascript engine.
And if Nintendo is hiding the web browser on security grounds, that's dumb too! Who cares if the browser is hidden—as long as it's accessible, the people who'd use it to hack their consoles will jump through whatever hoops are necessary. Making the browser hard to open only hurts regular users.
I find it more likely that the browser is hidden because it's too buggy and unstable for widespread use. I've played with it, and it likes to crash. A lot.
As for their efforts: They've made far more effort than they ever have before. Using homebrew or custom firmware effectively means you can't ever use that device online again (which wasn't the case for earlier consoles).
Are you suggesting that just because they've made mistakes that they would be in any way inclined to let the Ruby thing go?