3 ms·
I understand that. IMHO macOS should have both Maximize and Zoom as they do different things and serve different use cases (Apple seems to think that if you wan
by lloeki 3y ago
I understand that. IMHO macOS should have both Maximize and Zoom as they do different things and serve different use cases (Apple seems to think that if you want Maximize you actually want fullscreen, which kind of makes sense in a way, except not, e.g when one wants to still be desktopish and rely on cmd tab or cmd backtick, and because the fullscreen/tiling/spaces is crappily implemented for power users)
Now, in practice, Zoom is really nice when it works (I'm using it all the time with Finder+ windows), the problem is that it takes a single app not providing the content size hint for it to break and make it confusing. And then a vicious circle starts where more apps don't care about what it's supposed to do, and before you know it Zoom is mostly falling back to being Maximize most of the time, and people wonder why when it's doing the original Zoom thing it behaves differently and think it's weird and broken (which is perfectly understandable)
In a way Apple either did not embrace the winlin paradigm enough (e.g having a proper Maximize alongside Zoom + having an option for per window cmd tab) or they did not stick to their guns enough (enforcing Zoom to be correct + having a worthy fullscreen/tiling implementation) and we're left with a shitty compromise.
+ A very similar case that ties into this is how the Finder went from being fully spatial to a half-spatial half-global compromise.