The ability to learn is really irrelevant here, You could use that argument to justify anything. The point is that I shouldn't have to guess which button is intended when following an instruction. Having more than one button on the device with the same name introduces an unnecessary ambiguity.
It's not really guessing. If it's a native game, it's quite likely to use one of the game buttons; If it's a desktop app, it likely is using the keyboard; If it is an emulated console, it is likely to use one of the game buttons; If it is an emulated computer, it is likely to use the keyboard. I have never pressed the wrong key or button for A, B, X, Y, L, or R in the whole time I've had a Pandora, and I was one of the first 400 people to receive one. I don't believe that that has to do with me being incredibly lucky or having any special "skills". The majority of people should be able to do this. Those who can't, can learn the buttons easily enough.
That being said I have always always considered the terms key and button to be interchangeable when used in reference to (computer) keyboard keys. They may be called keys, but they are still buttons. The keys on the Pandora especially aren't what I would traditionally consider a key either, they have just inherited that name.
A keyboard is a board of
keys. While keys may be buttons, it does not make any sense whatsoever to call the keys on a keyboard "buttons"
instead of keys. As I said before, it's called a "keyboard", not a "buttonboard".
No, but say for example I decide to fire up a program I don't use commonly then I may not remember what keys it uses. If I'm relying on help texts to tell me the mapping I don't want there to be any guesswork involved in comprehending them. When you follow an instruction and you don't get the results you expect, you don't always know why, Certainly prior to this conversation "there are 2 buttons called that" wouldn't have been the first thing to come to mind.
This contradicts your argument that the user would not know which button to press. If they don't know which is the correct button to press, then they are obviously aware that two buttons with the same label exist, so "there are 2 buttons called that" should be the first thing to come to mind. Also, considering that
you are the one who suggested this feeble problem in the first place, I highly doubt you wouldn't think right away about how there were 2 buttons called the same thing.
Button are made to send information to the computer. There are many buttons because there are many information, labels are made to know which button send what information, so to differiantiate buttons.
Keys may tell you what information they send, but Game buttons do not. A Start button on a controller does not send the string "Start" to its host device.
Nobody need to tell you what button you shoud press because you should know what information you have to send by reading manual. Because of emulation, someone have to write somewhere, what information correspond to what labels that's all.
That's not true. If I'm talking to my friend, I will tell him tips and tricks about how to do things, often mentioning button combinations. I don't hand him a manual for the game. Users
need to be able to easily communicate which buttons they are speaking about.
-God Ginrai