‘A keyboard, how quaint.’
Was the single stupidest thing ever in Drek world, that’s saying something.

Can you talk as fast/clearly as you can type?
If you can, learn to touch type.

Consider saying ‘OK’ 6+ times vs, just banging the enter key to accept defaults.
Imagine working in a cubefarm with everybody using voice control…GD nightmare.

‘Querty, how quaint’ might have worked.

Duh, not everybody is the target market for everything.

And that’s fine.

Simpler is always better, so long as the job gets done.

KISS.

They should start teaching that to automotive engineers again.

That’s all voice control ever needed to be, and every system since then has been stupider by trying to be smarter.

The choice is clear for everything that has not at least a one or two minute time frame to be done … well, at least it should. I personally know a high risk implementation, where speech output may block other speech output until it is too late, grinding the system to an emergency stop. Earlier systems just used beeps, which were much more (time-)precise in output and recognition, and more than one beep could be played, recognized and reacted on at the same time. The speech does not contain more information than the beep did.
This is why I decidedly stand up against the one-size-fits-all narrative.

I will not have any of the commercial voice recognition thingies in our home. I’ve observed them in action at friend’s homes, and they are somewhere between a novelty and a nuisance. The owners end up shouting and repeating themselves, like they’ve hired a deaf aunt as a servant. I’m also reluctant to gift external entities with an open mic and free data.

But that’s the trick, right?

The voice recog system can do an infinity of things, and do it right most of the time. The button does the one thing, and it does it right absolutely every time.

And if your whole system is either that one function, or the infinity of buttons, the choice is clear. Real life lies somewhere in between, and it’s worth thinking about the tradeoffs.