This depends a lot on your workflow. I really like some of the features offered by yabai that depend on disabling SIP and installing the Scripting Addition. You

This depends a lot on your workflow. I really like some of the features offered by yabai that depend on disabling SIP and installing the Scripting Addition. You can totally use Yabai without this though. The biggest issue I have is that by disabling SIP, you can't use Apple Pay or use iOS apps on MacOS. The only 2 apps I wanted to use were Overcast and Apolo, so it's not a huge loss, but I'm still disappointed. The second issue is that the Scripting Additions were written for x86 and need to be completely rewritten for ARM (not totally sure about this, I don't know much about low level OS programming). This also means that the scripting additions behave a little erratically. The additions also need to be manually updated for every version of MacOS, so if a new version of MacOS comes out with cool new features, you need to wait for a yabai update before you can update your OS otherwise you end up breaking your config. Right now I also have a bug that means that I can't grant Yabai accessibility permissions so I just have it disabled while I wait for a fix. All in all, you're running a window manager on top of a window manager, so you're obviously going to end up with some weird behavior. Personally, I've put in several months of effort to making these 2 window managers play nice together and also _feel_ more like my linux install with features like remapping keys with karabiner, launching terminal apps with alfred, having a UI that shows your window manager shortcuts, and a panel that queries info from yabai. Is it worth it? If my job depended on it I would probably just use macOS as default, but since this is all on my personal device and I enjoy tinkering, I think it's worth it.