I like the flexibility, but I really really don't like people to hear what I'm saying. Imagine three people in a room trying to do this. It'd be total nonsense. Subvocal commands would be really nice, if that's a thing that is actually possible.
Or maybe constant chattering from everyone around you becomes the new normal. I can totally imagine old me (38 now) being completely overwhelmed by this technology and all my grandkids wondering why I'm having such a hard time, and rolling their eyes when I say I just want a mouse and keyboard, dammit! Everything was simpler back then! I didn't have to listen to all this yabbering all the time and I could just tell the dang computer what I want it to dang darn do!
About the same age, and I feel this way about mobile devices/touchscreens already!
I can't stand touchscreens for anything other then placing calls, and maybe controlling music playback. Anything more complicated I miss dedicated hardware for input.
I have tried to more or less replicate this setup, but found it less satisfactory. Aside from it demanding near-perfect audio quality to work remotely well in general (as well as a heavy time investment, initial and ongoing), you frequently run into edge cases where it just doesn't want to understand something you're saying. After the 5th or 6th mis-transcription of some specific phrase, you tend to just give up and reach for the keyboard, RSI be damned. (And this as a native English-speaker, with a relatively neutral accent.)
I can definitely imagine better fleshed out solutions to either voice recognition for programming, or programming languages whose syntax lends themselves to easier and more productive voice recognition. I could see some definite productivity enhancements if it were achieved.
Currently our programming is optimized for keyboard input. If sub-vocal instruction becomes "a thing", I suspect we would spend some collective effort to create a programming language optimized for that mode of input.
I think the only reason we don't have real languages using touch input is because of the lack of bandwidth for that signal.
Ironic now, that probably 50% of my interactions with computers are via command line.
Plus, talking all day is exhausting. Why would you want to do that?
I wouldn't hold my breath.
Was that acronym in common use at the time that the book was written? How about the movie? Which way does that causation go, if it exists at all?
Sorry for the off-topic question, but it really does haunt me. Modern HALs are like rat nests, and I imagine it was worse in decades past. So it must be a pun...right?