4 ms·
>especially with scanning each binary you run You do realize you can disable a healthy chunk of this stuff, right? A dev might not want it, but end users (non-
by Klonoar 5y ago
>especially with scanning each binary you run
You do realize you can disable a healthy chunk of this stuff, right? A dev might not want it, but end users (non-technical, as much as this term annoys me) benefit from it.
Disable SIP (recovery mode dance) and disable GateKeeper (spctl) and you're off to a decent start.
They even document it, it's not hidden: https://help.apple.com/xcode/mac/10.2/index.html?localePath=en.lproj#/dev9b7736b0e https://help.apple.com/xcode/mac/10.2/index.html?localePath=...
- pdimitar 5y agoOh yeah, I am aware. But I don't buy a Mac to tinker with it. The huge price mark-up is for the "it just works" part in the package. Plus I am very scared when it comes to Mac security. I am pretty sure that to this day their mitigation strategy is "almost nobody is writing viruses for Mac anyway". :D I will not risk disabling SIP especially with programs like Chrome on my Mac. The sad part is that they _can_ make it work better and be faster but they don't want to. That's why in a few years time my iMac Pro is simply going to be the most expensive day-to-day desktop machine in a 1km radius and I'll use a cheap Ryzen laptop (or expensive Threadripper workstation) for actual work.
- Klonoar 5y ago>I am pretty sure that to this day their mitigation strategy is "almost nobody is writing viruses for Mac anyway". :D The very existence of SIP/Notarization/a bug bounty program/etc indicates their stance is otherwise. ;P