Input isn't always the bottle-neck. I think far slower than I type. Actually, a keyboard with editing commands (for cut, past, word select ... the basic VIM /

Input isn't always the bottle-neck. I think far slower than I type. Actually, a keyboard with editing commands (for cut, past, word select ... the basic VIM / emacs commands) and special keys along with a mouse and voice input could be optimal. Programming is a special case, but I think programmers can cope. The languages might have to change. IIRC, C still uses the ";" instead of newlines, because that was optimal for punch cards, but more modern languages often don't. Most people just want to churn out emails and tweets, though. The big issue is, people use much more complex grammar than when they write. It's fine if you're listening (since the human brain is really good at parsing spoken words), but reading what the average person will produce on a speech recognition system will be brutal. Example: It's amazing how people speak - they use split phrases, and they have long run-on sentences; often with embedded subclauses; which go on and on and are really quite complex but then they trail off when they forget what they were talking about. Oh yeah, I think it was how speech recognition is might have unexpected consequences or something.