[atticus_]

yabai uses native macos spaces and generally requires sip to be disabled to have a good experience(windows can't be moved between spaces without)

rift is essentially aerospace but implemented in a yabai style. yabai style meaning using low level, private apis and generally focusing more on performance. whereas aerospace prides itself on only using one private api.

usage wise, aerospace and rift both use a virtual workspace system where all of your (work)spaces are in one macos space so no red tape has to be cut in order to move windows from ws -> ws and so forth

[mgrandl]

Does rift handle native MacOS tabs like the ones ghostty and finder use? I might give it a shot. I have been having a couple of issues with Aerospace lately.

[yongyongyong]

Same. That's the worst part of Yabai

[bartvk]

No, rift also has problems. For example, if I have Calendar on the left, and Finder on the right, and I open a tab in Finder, then it looks like it works.

However if I close the 2nd Finder tab, then Calendar maximizes below Finder.

[mgrandl]

Also I am wondering if you could estimate how difficult it would be to implement something like Niri? I much prefer the scrolling style tiling, but none of the MacOS WMs seem to be going that route (other than PaperWM.spoon which is not for me).

[atticus_]

to answer both comments: i've been working on a way to handle tabs but it's hard to find a solution that isn't half-baked due to the lack of info on tabs given by the os (there are no events or anything, just on a11y attribute that give info on tabs)

as for a scrolling layout, its possible, but does not fit that well with rifts layout, even thought you can get something similar using trackpad swipes to switch between workspaces

[autrilla]

https://github.com/karinushka/paneru does that

[malnourish]

I'm pretty new to Mac and didn't know Paper had a port, what isn't to your liking?

[__mharrison__]

I'm using aerospace. If I'm fine with performance, does rift provide anything else?