It matters. The menu location (and the keyboard shortcut) for Print has been in the Apple Human Interface Guidelines since the 1980s, and all Mac apps adhere to this convention.
You might be able find an exception -- there is no approval process for HIG in Mac apps. But you will not find an exception (v1.0.1 or later) in an app that has any meaningful user population, or is of any meaningful quality.
Ignoring HIG without good justification is a strong garbage signal. It was a surefire indicator of a crap Windows port back in the 1990s, but I don't think that's even a thing any more.
The Mac app ecosystem considers HIG failures to be serious bugs, and they do not survive. So yes, for all meaningful definitions, "all Mac apps adhere".
You do not appear to know what you're talking about here, and I don't know why you're bothering to argue. Show me an example of an even semi-popular Mac app which uses a different convention for Print, and we might have a conversation.
Your excerpted quotes are misleading, but I'll respond to one point:
> most of these defaults are poorly (unergonomically) engineered based on design ignorance from the 80s
You just invented that problem. Show me a more ergonomic design for Print. A large part of design/usability success is consistency and predictability.
I have yet to see how the defaults of windows are more ergonomic. I am also not aware that humans have significantly changed as a species since the 80s, so all the the ergonomic considerations are the same.
Besides, it completely misses the point - ergonomics are often about convenience and knowing what to expect. A zoo of frameworks and UI paradigms is a most terrible outcome with any kind of HIG. Microsoft is not able to keep a consistent UI paradigm for their own software - what a shining beacon of chaos they are.
I have yet to see how I stated that Windows defaults are more ergonomic. And your limited awarenes ignores the fact that ergonomic considerations were not properly taken into account in the design in the 80s just like now there are still plenty of ergonomic issues
Given that the convention seems more often followed on macOS can't it be a property of the environment of macOS developers usually following the conventions better than on Windows?
Even if not an inherent property of the system it's an emergent one, something causes it if it's not restricted by the system itself but is still a property that apps developed for macOS are much more homogeneous in their menus UI implementation than the others.
If you shroud this basic misunderstanding in so much emergent mystery, sure, but otherwise no, and the real reason is simple enough - that's just one of the defaults in some "UI kits", which macOS devs can also use, including "disparate or bespoke" ones, and could've been just as consistent without it being positioned at the single top spot
Can we agree that it could be a 2nd or 3rd order effect of a design choice such as putting the menu system as part of the system's UI nudging developers to follow conventions instead of inventing their own menu UI because it resides inside a window which they can control completely, hence giving the thought of "I can do the menu however I want" a bit more probable?
It's hard to analyse and quantify this ergonomics objectively so I'm just spitballing a potential way that the menus in Mac apps follow much more the convention than Windows apps. I think Apple is also much better at keeping their UIs consistent than what the Windows team is, could also be another nudge to developers to follow them. And no, I'm not saying they're perfect, I hate all their UIs like the App Store, new System Settings (it's frankly stupid, also in responsiveness), Apple Music, etc.
Design choices are nudges, Apple's ecosystem has nudged developers much better into keeping some consistency across the system, it's much more jarring on macOS when an app doesn't follow conventions than on Windows.
> just an unenforced convention that you can adhere to on Windows as well
And yet on Windows I often have to do a Where’s Waldo for certain options or even submenus. On macOS it has been crystal clear where to find these options for almost 25 years if we count from Mac OS X, and you can trace some the lineage back all the way to Mac OS 1 which was launched 40 years (!) ago.
The thing that has finally started to chip away at this steely adherence to UI conventions is nothing other than poorly made Electron applications, which ironically Linux can actually get nice menu options for via Dbus trickery :)
