Comment: Let's all guess at what our software does (Score 1) 449
While I know some people love search boxes on everything, I personally use them as a last resort. Inevitably it takes me more times and more interfacing (mouse or key clicks) to accomplish the exact same thing that a well written menu can do.
The argument that they present for why the HUD is great is exactly the reason why it is a poor replacement for menus. Menus are more than triggers for functions. They tell the story of what the software can do. For example, I use a lot of different graphics programs. Some have certain filters that others don't. Some filters are named differently in different programs. Sometimes there are brand new filters that I am just beginning to learn the names of. Sometimes I see a filter in a menu that I have never used and say "oh, let's see what this does". In all of these cases, a menu system beats a search box every single time - and the same is applicable to other kinds of functions in software.
If a solution requires someone to know the first letter of a command, then why not teach them to better use keyboard commands? Or perhaps come up with a way to better organize keyboard commands in a way that easier for a regular users to understand? Search boxes have their place, but they are not the best at being a primary point of accessing functions from a finite, predefined list.