2 ms·
> Here's an example: panes, tabs, windows, apps, spaces. These things all fight against each other, have their own little silos, get treated differently by ever
by cosmic_cheese 10mo ago
> Here's an example: panes, tabs, windows, apps, spaces. These things all fight against each other, have their own little silos, get treated differently by every single app, etc, etc.
Disagree. The fact that these are independent is a huge organizational boon for those who know how to apply some combination of them.
Example: I set up spaces (virtual desktops) to have themes: one of general web, one for iOS dev, one for Android dev, etc. within that, it’s useful to be able to further organize with windows and tabs — windows can represent projects for example, and tabs can represent files. These work together to prevent a Cambrian explosion of windows that would be impossible to manage no matter how your environment works.
It’s useful for apps to be distinct from windows, too. This allows things like moving all windows belonging to a particular app between screens, or minimizing/maximizing them all, hiding them all, etc. Panes in most circumstances are an entirely different beast than tabs and windows… it wouldn’t be useful to turn an inspector palette into a tab.
They work together as long as one’s mental model isn’t overly simplistic.
- oneeyedpigeon 10mo agoI didn't really explain my objections very well in such a throwaway statement. My issue isn't that those things exist; pretty much the opposite. I think it's good that they exist and they almost certainly always should. My problem is when app A implements tabs differently from app B, app C uses the same shortcut for switching windows that app D uses for switching tabs, etc. It just all seems so disjointed. What I want is for an OS that treats things like tabs as first-class citizens, not a byproduct that each app implements in its own way.
- cosmic_cheese 10mo agomacOS actually has native tab support built in. It supports everything you’d expect from a tab system, including merging windows into tabs and splitting them back out. All third party devs have to do is opt in and tell the OS which windows are intended to participate. It’s been a feature for a long time now. Problem is that most third party apps don’t opt in and instead reimplement tabs themselves. It’s mostly native Mac apps made by small boutique developers that use native tabs.
- crazygringo 10mo agoIs it enabled by default? I only very recently changed my System Settings > Desktop & Dock > Windows > Prefer tabs when opening documents to "Always". I'm pretty sure the default is "In Full Screen". Now, something like TextEdit creates new files in new tabs rather than new windows. It's great! But by default, everything on macOS seems to use windows rather than tabs. I don't even think most people know about the "Prefer tabs" option at all.
- anon7000 10mo agoTab support is definitely enabled by default — eg cmd-T in finder to make a new tab
- crazygringo 10mo agoI'm not talking about Finder. I'm talking about default behavior across all relevant apps, apps like TextEdit. When you create a new document, does it open in a new tab or new window by default?