Overly dismissive of CLI, but I'll excuse that.
Overly dismissive of CLI, but I'll excuse that.
I think the version shown at 59m9s is complete:
https://youtube.com/watch?v=AItTqnTsVjA&t=59m9s
Editing lightly:
1. The GUI should be asthetically acceptable with heavy and long use.
2. There is no perfect GUI for everyone.
3. There are many features that are ideal for the majority of users.
4. The GUI should get out of the way when you don't need it.
5. The GUI should be as efficient as possible if you know what you're doing.
6. The GUI should activate when you want it and not when you don't.
7. It shouldn't be easy to do things you don't want by accident.
8. Switching between mouse and keyboard should be minimised.
9. Use multiple mouse buttons for maximum efficiency.
10. Both low-contrast textual and stark contrast graphical elements should be avoided.
I'm not in full agreement (#3 may be debatable) and would add a few items (especially: preserve user state if at all possible). But it's a good starting point for discussion.
>The visible graphical interface features of an application are sometimes referred to as chrome or GUI (pronounced gooey).[11][12]
It is also Gif not Jif or Gee I eff. :-p
people also pronounce "GAN" (Generative Adversarial Network) with a hard G even though Generative is a soft G (J).
and how do you pronounce "MUA" (Mail User Agent)? I'd go with moo-ah, even though it's not a Mail Oozer Ahgent :)
(Just kidding. But I’ll say it with a hard G until the day I die. Because...G)
So is at least one third of the English language…