That's all well and good, but when I've closed the interfaces with which I'm interacting with the Chrome "service", isn't it pretty clear that the intent is that "I'm done with the service"? "Chrome team chose to build it like that" -- I guess the question here is "why is this even an option at the OS level?" and "shouldn't we expect window and application behavior to be consistent?". Davinci Resolve on macOS, for example, exits when I close its window while Chrome does not. Do you not think that even having this option to create an inconsistent application interaction seems like bad design? Sometimes the app exits when I close all windows, sometimes it doesn't.
My issue with the menu bar is purely from an ergonomics and usability perspective, especially with high resolution monitors. If I have a window at the bottom right corner of the monitor, I need to move my mouse all the ways to the top left of the monitor to interact with the menu bar. If you always full screen everything, it makes total sense. But I would make the case that macOS has done a very poor job of adapting to changes in monitor resolutions. Consider ultra-wide screen monitors where I have apps side-by-side or I have 4 windows tiled. The accessibility of the menu bar becomes quite low for three out of the 4 windows.
The key stroke to access the menu bar is (do you know it?) CTRL+F2. Try that stroke yourself and see how it feels. It's not at all obvious that this allows you to access the menu bar with the keyboard.
By attaching the menu bar to the application window, the spatial locality increases usability, especially for modern ultra-wide monitors don't you agree?
I do agree that you have a point. But it’s an interaction model that works for many people and there are customization options to alleviate some of the pain points from keyboard shortcut (administrated at OS level) to 3rd parties software. I don’t think it’s reasonable to expect a complete reworking of the interface.
My issue with the menu bar is purely from an ergonomics and usability perspective, especially with high resolution monitors. If I have a window at the bottom right corner of the monitor, I need to move my mouse all the ways to the top left of the monitor to interact with the menu bar. If you always full screen everything, it makes total sense. But I would make the case that macOS has done a very poor job of adapting to changes in monitor resolutions. Consider ultra-wide screen monitors where I have apps side-by-side or I have 4 windows tiled. The accessibility of the menu bar becomes quite low for three out of the 4 windows.
The key stroke to access the menu bar is (do you know it?) CTRL+F2. Try that stroke yourself and see how it feels. It's not at all obvious that this allows you to access the menu bar with the keyboard.
By attaching the menu bar to the application window, the spatial locality increases usability, especially for modern ultra-wide monitors don't you agree?