This is the part I absolutely don’t get about this. Plus windows create a better visual boundary for the context-switch tab groups are supposed to be as you minimize one and restore another.
Why not just use windows? 🤷 I sure hope they keep the implementation of this simple and end up just doing that for the user. Create new tab group -> color-coded new window opens up, gently nudging the user towards how simple the solution to their problem actually is.
Tab groups in chrome are something I dearly miss from chrome. It’s super convenient for grouping projects and quickly switching between them. Multiple windows is a worse experience: there’s no preview favicon or anything to indicate what a window is actually for until you hover over it. With a tab I can see at a glance what something is before I switch.
For real, I already have different groups for tabs, they’re called windows.
But now I will be able to have tabs within groups within windows within desktops!
This is the part I absolutely don’t get about this. Plus windows create a better visual boundary for the context-switch tab groups are supposed to be as you minimize one and restore another.
Why not just use windows? 🤷 I sure hope they keep the implementation of this simple and end up just doing that for the user. Create new tab group -> color-coded new window opens up, gently nudging the user towards how simple the solution to their problem actually is.
Tab groups in chrome are something I dearly miss from chrome. It’s super convenient for grouping projects and quickly switching between them. Multiple windows is a worse experience: there’s no preview favicon or anything to indicate what a window is actually for until you hover over it. With a tab I can see at a glance what something is before I switch.
Every instance of the same program eats memory