alt Hacker NewsIt's an interesting point, but I think the benefit of having actions related to the main object(s) that each application deals with in a standardized place that people expect ("File") outweighs the cognitive load of needing to figure out where those actions might be in every single program.
Replies
xattt • today at 7:40 PM
Applications that don’t use the “File, Edit, View, [App Specific Menus], Window, Help” structure are really weird to use.
Example: a bunch of JRE apps on OS X. Circa mid-2010s, many didn’t follow the standard menu layout and were a little jarring (pun intended) and unsettling to use when you tried to navigate features.
Yes. It’s all about consistency and user expectations.
Apple guidelines for example, which have been in place for 40ish years:
> Best practices: Support the default system-defined menus and their ordering. People expect to find menus and menu items in an order they’re familiar with. In many cases, the system implements the functionality of standard menu items so you don’t have to. For example, when people select text in a standard text field, the system makes the Edit > Copy menu item available.
https://developer.apple.com/design/human-interface-guideline...