But largely I agree with you. I wish Apple had taken longer to fully develop a robust solution from the ground up instead of the status quo of piling on year after year to a semi-broken system.
But largely I agree with you. I wish Apple had taken longer to fully develop a robust solution from the ground up instead of the status quo of piling on year after year to a semi-broken system.
...see, I actually had the opposite frustration with SIP. So many people were so hesitant to turn it off, even when they had a clear use case.
This is where the argument looses me. I agree that it's good to protect people from screwing up by accident. But if someone has taken the time to reboot their computer into recovery mode, find the Terminal app, and run a very specific command, that is not an accident! That is a user clearly requesting that the training wheels be removed. And sure, maybe the user was following bad advice, but it wasn't an accident!
People are allowed to do stupid things, that's how we learn. Again, it's great to have guardrails for people who want them, and it's great to have those guardrails on by default for people who don't want to think about them or even know they exist. But deciding which users are savvy enough to be worthy of disabling SIP feels Gatekeepy to me.
https://support.google.com/chrome/thread/15235262/chrome-upd...
The Chrome updater could also have had a bug that completely deletes your home directory, and SIP wouldn't protect you. I guess your computer would still boot in that case, but how much would you care? The actual damage would be worse.
Anyway, this entire incident was notable precisely because it was so unusual—in ~9 years of SIP I'm not aware of any other instances where turning it off caused problems.