I'm quite torn on this (to be fair, I rarely use voice commands at all...I've found it's usually more effort to fix things when it gets it wrong than the cumula

I'm quite torn on this (to be fair, I rarely use voice commands at all...I've found it's usually more effort to fix things when it gets it wrong than the cumulative sum of all the times it may save me any time whatsoever). 1. I can see how this is absolutely frustrating for someone who uses one of these commands regularly. 2. At the same time, one of the issues with voice commands relative to say keyboard input is the lack of delineation. If I hit Ctrl + Enter on my keyboard, there's no way for the computer to interpret that any differently. However, that's not the case with voice commands. It needs to keep determining (a) what I said, (b) whether it's a command or just voice, (c) whether it's a command it's supposed to execute and that's before it even figures out waht to execute. But the problem is that as the number of voice commands increases, the number of false "this is a command and not just voice" triggers will increase. There's probably a genuine benefit for Google's users in the universe of commands being very small as long as the command that's removed is not one they use. I've noticed several of the options are "you can use a custom routine to do this instead". Maybe Google should have included the custom routine and made it togglable.