Re:Changes we're making to Google Assistant
by dotancohen on Friday January 12, 2024 @07:07PM
(#38975894)
What's wrong with that? In VIM I like the fact that there is no interface cluttering my workspace. If I need a feature, I search for it online.
[ Parent
| on HN ]
VIM is well designed and stable, so you can learn the interface and be confident that it will work for you next time you use it. It's an amazing tool.
Today's voice assistants are the opposite. They are unreliable and completely unstable. They don't have a clear list of commands they understand, let alone some sort of menu system - the documented commands on the manufacturer's websites often don't work. They also randomly change what they can do: stuff stops working for no obviously reason.
For example - yesterday, my son's Nest Audio suddenly refused to set a music alarm, claiming "this device doesn't support that feature yet" (it's literally a speaker for music...). It worked the day before.
Re:Changes we're making to Google Assistant
by dotancohen on Saturday January 13, 2024 @06:46AM
(#38979114)
So the problem is with lack of documentation and unstable UI, not with the lack of discoverablility per se.
Identifying the problem is often the first step in fixing it.
Vim has an actual manual and things stay relatively stable across releases. It's not the case for the voice assistants, where stuff breaks randomly and features are added/removed without notification.
Re:Changes we're making to Google Assistant
by dotancohen on Friday January 12, 2024 @07:42PM
(#38976165)
Well then the problem seems to not be with the fundamental lack of discoverablility by UI poking, rather at the lack of official documentation.