3 ms·
Mainly DOS/Windows user from ~1992-2000. Mainly Linux 2000-2011. Mac since. > The moment macOS is shackled any more I hadn't really noticed it being "shackled
by bamfly 3y ago
Mainly DOS/Windows user from ~1992-2000. Mainly Linux 2000-2011. Mac since.
> The moment macOS is shackled any more
I hadn't really noticed it being "shackled" at all. What do you mean?
- ndiddy 3y agoIf you don’t have an Apple developer account and you give a program you wrote to someone else, their computer will refuse to open it unless they go into System Preferences and whitelist the program.
- Our_Benefactors 3y agoThis is intentionally misleading. Running any unsigned package requires the end user to open the program through system preferences for the first time, as a “did you really mean to run this potentially pwning software”. It’s a good security practice, and less intrusive than windows UAC by far.
- ndiddy 3y agoWith Windows UAC, when you run a program it opens a pop-up saying "do you want to run this program" and you can click "yes" to continue. With a Mac, if you run an unsigned program it opens a pop-up saying "program cannot be opened because the developer cannot be verified" and your options are "Move to Trash" or "Cancel". It doesn't mention anything about letting you open the program anyway. This means that if you want to develop software targeted at anyone who doesn't know to go to the security section in System Preferences when they're not prompted to do so, you have to pony up $100 for a developer license. A lot of open-source projects don't offer Mac builds for this reason, and you have to build from source instead.