That kind of thing sounds like an excellent fit, especially for the programs shown in the accompanying video. Some things just work better with a visual interface - web browsing, graphics work, etc - so the ability to get away from the graphical sparseness of a CLI implementation while keeping its speed and expressiveness sounds like an excellent compromise to me.
The HUD proposal of Shuttleworth, on reading, is actually somewhat similar to how vimperator presently works. I can activate the statusbar with a ':' (same as in vi), and either hit tab or start typing. Though I don't get teh shinay overlay transparent displays, I'll get a list of completions for commands, URLs, bookmarks, etc.
Which is great when you're in front of a keyboard. When I'm using my phone (Android), I'm often annoyed at how niggly the interface is, and how much typing I have to do, in an environment which really does NOT support it well.
There are also users who simply learn things by rote. They don't know the commands, they don't understand the process, they simply click on a known element or (rarely) type something -- rarely more than their username or password. "My mom" or "Aunt Tilly" are the classic (if sexist) examples, but the former is certainly accurate in my case. She actively fears computers and loses about 50% of her confidence the second you park her in front of one.
As much as I think I'd like the HUD, I really do NOT think it would work for her.
Which is where Ubuntu is getting schizoid. For the past five years, it's seemed that the distro has been aiming for wider and broader appeal, with ease-of-use functions that appeal to the 99% (or more accurately, the 99.99%) -- the technologically naive (or illiterate, if you prefer). Which really pisses off this particular element of the 0.01% when I'm stuck on that interface.
It appears that the distro's taking a hard tack in the opposite direction now.
My own suggestion: do NOT aim for a one-size-fits-all interface. Simply ain't gonna work. Sure, all you Mac users will try to convince me otherwise, but aqua's an interface I find myself grossly stymied in.
Conventions also matter. Most Linux and GNU utilities offer:
- manpages (or, deprecated, info pages) - a brief help with some variant of "-h|-?|--help" - package information under /usr/share/doc/, generally with a pointer to upstream.
They'll often include readline command editing, command completion, and other features, all very useful.
Systems such as Debian's 'dwww' (built in web-enabled documentation integration) allow accessing all of this and more through your browser, if you prefer.
Not all utilities offer this. I've seen more than my share of proprietary CLI tools with very, very poor documentation and discoverability, so this isn't something that's inherent to CLIs. But it's certainly doable.
I see some 3200+ commands available on my search path, plus shell builtins and functions. My shell history includes fewer than 200 ($HISTSIZE=3000).
The situation for GUIs is very nearly always worse. Except for minimal interfaces, it's difficult to present more than a dozen or so options at a time. Some level of predictive completion may help, but in doing so you're starting to bridge the divide between a pure menu and a CLI.
I've found myself preferring CLIs increasingly, even in nominally GUI tools. The vimperator plugin for firefox claws back crucially useful vertical real-estate while offering a very powerful interface to my browser.