I don't think there's anything macOS is doing better than Windows in so far as UX goes. Put it another way: I use macOS every day and I never think "Wow, I wish Windows had this feature, too" but every day I wish I had some UX element from Windows -- just basic window management feels so clunky on macOS unless you fullscreen everything.
Hardware is great, though.
When you're close all Chrome windows, that just means you're done with the webpages, not that you're done with Chrome. Chrome dev team can set Chrome to terminate when all windows close, but they've not chosen to do so. It's there when you want to create a new window when you want to interact with a new webpage. And again it's up to the developer to choose to tie the application lifecyle to its windows.
> MacOS applications are more like services,
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?