Too many people equate speech to text as 'speech recognition' and it clearly isn't. What is not a solved problem is Natural Language Processing. That NLP isn't solved, is a fertile source of papers. What is 'kinda' solved is the voice CLI, that is where speech is converted to text, that text is inserted in a class command interpreter, and if recognized the command is executed, otherwise it isn't.

Nobody expects to be able to type 'find me the files that changed yesterday' into a computer shell and have it do something sensible. But 'find ./ -type -f -mtime yesterday' sure we can expect that to work. Getting from the first one to the second one requires something called an ontology.

I worked on a team at IBM that was building this sort of capability. The plan was that in conjunction with an excellent tool kit for disassembling a sentence into its component parts (verbs, nouns, adjectives etc) and then matching the elements recognized with an onotology associated with that action. 'find' being the verb would select the search action ontology, 'files' as an object of the verb would select the computer files object ontology, and then 'changed' and 'yesterday' would match 'modification' in that ontology and 'yesterday' would match one of the two sub children of 'modification' (time and change-actor). Then you would go back with what was the compiler equivalent of an abstract syntax tree which the 'command generator' would use to emit the necessary command actions and flags.

I have no idea why they cancelled it. It was an inscrutable place to work at in many ways :-).