MacOS repeatedly got in my way when trying to run specialist software needed for my work at [organization], because I had the audacity to use an executable not in line with Apple’s walled garden. Additionally, transferring files was a pain in the nuts - so many “mac moments” of files resulting in 0 bytes after drive ejection and repeated permission error messages despite having the appropriate credentials active.
Throw in some minor annoyances with frankly unintuitive UX for general settings and layout configuration, and I was sick of the damn thing by day 3.
Made me miss my old job where I got to smash a vacated lab’s worth of Macs with a sledgehammer. And where I was allowed to bring my own laptop.
I don’t think it’s fine. Expose the option, then warn me of the consequences, and allow me to decide. Warn me several times if you want, but allow me to disable it.
It’s quite rare to run into a Gatekeeper warning. Most users probably won’t ever see one. And if they do, they can still bypass it for an individual app using the UI. It’s just a bit convoluted (by design).
I administer a bunch of Macs for a university and I actually block the ability to disable or bypass Gatekeeper and nobody has ever complained about it.
MacOS repeatedly got in my way when trying to run specialist software needed for my work at [organization], because I had the audacity to use an executable not in line with Apple’s walled garden. Additionally, transferring files was a pain in the nuts - so many “mac moments” of files resulting in 0 bytes after drive ejection and repeated permission error messages despite having the appropriate credentials active.
Throw in some minor annoyances with frankly unintuitive UX for general settings and layout configuration, and I was sick of the damn thing by day 3.
Made me miss my old job where I got to smash a vacated lab’s worth of Macs with a sledgehammer. And where I was allowed to bring my own laptop.
You can disable Gatekeeper entirely using the terminal. They just don’t expose the option in the UI anymore (which I think is fine).
I don’t think it’s fine. Expose the option, then warn me of the consequences, and allow me to decide. Warn me several times if you want, but allow me to disable it.
It’s quite rare to run into a Gatekeeper warning. Most users probably won’t ever see one. And if they do, they can still bypass it for an individual app using the UI. It’s just a bit convoluted (by design).
I administer a bunch of Macs for a university and I actually block the ability to disable or bypass Gatekeeper and nobody has ever complained about it.
They do exactly that. You just use a keyboard instead of a mouse to accomplish the task.