> The added functionality with this approach is that you can use the Space as a casual grouping of windows in a related project. The cool thing about this is h

> The added functionality with this approach is that you can use the Space as a casual grouping of windows in a related project. The cool thing about this is how well this mixed approach copes with the command-tab switcher; you stay local to the space until you tab to a thing that is in another space, which can make for really useful working patterns if, for example, you use site-specific browser apps for different online roles. For me it is regularly VS Code full screen in one space, browser and another app (Apple notes, a messaging app or tailed server log in terminal) together on another. But the difference between how Spaces works and how the WM in the demo video works seems like night and day. For all my frustrations about the way changing the app in one half of a Space can work [0], the Apple interface is at least an attempt to produce something that is driven by obviousness and gestures, in the way that (as a veteran mac user can tell you) that the "menu bar across the top of the screen" model is more instinctive and quicker to interact with than each modal having its own menu. The system in the demo video is jerky, hyperactive and surprising. I'd rather accept the limitations of a simpler approach designed to avoid level of surprise and jitter. [0] Not as well as iPadOS does. Never thought I'd say that sentence.