|
macOS only recently got an option to make windows fill the screen. For most of history what most people would assume is a maximize button (the green one) was actually a zoom button. It sized the window to what the OS thought was appropriate for the content (to the best of my knowledge and experience with it). Apple then made things go full screen, but in a special full screen mode, so macOS worked more like the iPad. By the time they added a way to maximize windows in the way Windows does, the idea of maximizing an app has largely worked its way out of my workflow. It was always too much trouble, and I find very few apps where it provides much benefit. Web browsers, for example, often end up with a lot of useless whitespace on the sides of the page, so they work better as a smaller window on a widescreen display. In an IDE, it really depends on what’s being worked on and if text wrapping is something I want. Ideally lines wouldn’t get so long that this is a problem. With the way macOS manages windows, I often find it easiest to have my windows mostly overlapped with various corners poking out, so I can move between app windows in one click. The alternative is bringing every window of an app to the front (with the Dock or cmd+tab), or using Mission Control for everything, neither of which feels efficient. I could install some 3rd party window management utility, I suppose, but in the long run, it felt easier to just figure out a workflow that works on the stock OS, so I can use any system without going through a setup process to customize everything. It’s the same reason I never seriously got into alternative keyboard layouts. |
Full screen one. Switch to the other. Now, use just cmd-tab and cmd-` to get to the full screen safari window (cmd-` switches between windows in the same application, which is literally never the right thing, but I digress).
For what it's worth, the third party tool 'altTab' mostly fixes this.
Bonus MacOS UI bug: I had to exit altTab to confirm they still hadn't fixed cmd-`. When I re-opened it using cmd-space, finder defaulted to the version in ~/Downloads instead of /Applications, then read me the riot act about untrusted software trying to change accessibility settings.
One more thing: I'm still not using MacOS 26, so all my complaints are about the "last known good" release.