I’ve been experimenting with macOS tiling window managers.

Amethyst was easy to install and required no deep system changes, but it had several drawbacks:

• No simple way to export GUI configs.

• Config keys felt confusing.

• Required “reset layouts” often.

• In multi-monitor setups, it sometimes ignored large screen areas.

yabai appears far more powerful, with true tiling, scripting, rules, padding/gaps, and a very active ecosystem.

But: on Apple Silicon macOS 13+, meaningful yabai features require partially disabling System Integrity Protection (SIP).

This feels risky. It’s unclear whether the security trade-off is worth the improved workflow, and whether I would later regret degrading the security posture of my personal laptop.

Resolution Criteria

This market resolves YES if, in my explicit judgment, disabling SIP (even partially) to run yabai would have been something I regret—for reasons such as security concerns, breakage, instability, maintenance overhead, or general dissatisfaction.

Resolves NO if I conclude that:

• disabling SIP would not have been something I regret, or

• keeping SIP fully enabled and not installing yabai would not be something I regret.
  

It resolve N/A if there's no convincing argument. There being only 1 argument won't make it convincing.

Resolution will be based on my clear written statement.

Trading Encouragement

Traders are encouraged to provide convincing arguments for their position, backed by reasoning or experience. Useful angles include:

• Security implications of disabling specific SIP components

• Practical experiences running yabai under partial SIP disablement

• Likelihood of future macOS updates breaking the setup

• Productivity benefits vs. long-term maintenance costs

• Whether lightweight alternatives (e.g. Amethyst, LeaderKey) already solve the core problem

• Comparisons with Linux tiling workflows and expectation management

Arguments that carefully weigh trade-offs or reference real-world experience are especially valuable.