4 ms·

Presumably what you mean is "if IBM locked down their PC as hard as Apple currently does iOS," because MacOS isn't locked down at all.

bombcar 3y ago
macOS is pretty hard locked to the hardware which is what OP is describing. And it’s easy to know how it would have turned out - as a footnote in the computing world as some other clonable system took over
sho_hn 3y ago
macOS is quite locked down. It's not possible to easily distribute software to macOS users that isn't code-signed and notarized, both of which require a paid Apple Developer account and Apple's participation. This is also true for "side-loaded" apps, not just ones distributed via the app store. Yes, it's possible to run arcane shell commands to unset extended file system attributes to circumvent quarantine, but this is not "easily".
- ubermonkey 3y ago
  I know some Linux zealots think that if there's literally ANYTHING preventing a random binary downloaded from DefinitelyNotMalware.com from running, then it's "locked down," but that doesn't make it true. These same people seem to love to describe the Mac environment as a restrictive, nannyware-controlled hellscape, but this, too, is untrue. The Mac is open, but ships with sensible defaults because MOST PEOPLE HAVE NO BUSINESS RUNNING APPS THAT AREN'T VERIFIED. Macs ship with an option set in the Privacy & Security pane that limits apps to those from the App store -- but it's a radio button, and the other option is easy to choose ("App store and identified developers"). Yes, this still requires the code be signed, which is a 100% reasonable position in today's world. And yet: that's not even the end of it. If you do download something from an unsigned source -- either because it's built from source, or because it's from someone who is ideologically opposed to joining the dev program at Apple, or whatever -- all you have to do is right-click the icon and choose to open it. That will save it as an exception, and allow it to be run normally after that point. See: https://support.apple.com/guide/mac-help/open-a-mac-app-from-an-unidentified-developer-mh40616/mac https://support.apple.com/guide/mac-help/open-a-mac-app-from... At no point do you need to resort to "arcane shell commands" or "extended file system attributes." In fact, literally ALL of this is absolutely easy.

bombcar 3y ago

macOS is pretty hard locked to the hardware which is what OP is describing. And it’s easy to know how it would have turned out - as a footnote in the computing world as some other clonable system took over

sho_hn 3y ago

macOS is quite locked down. It's not possible to easily distribute software to macOS users that isn't code-signed and notarized, both of which require a paid Apple Developer account and Apple's participation. This is also true for "side-loaded" apps, not just ones distributed via the app store. Yes, it's possible to run arcane shell commands to unset extended file system attributes to circumvent quarantine, but this is not "easily".

ubermonkey 3y ago
I know some Linux zealots think that if there's literally ANYTHING preventing a random binary downloaded from DefinitelyNotMalware.com from running, then it's "locked down," but that doesn't make it true. These same people seem to love to describe the Mac environment as a restrictive, nannyware-controlled hellscape, but this, too, is untrue. The Mac is open, but ships with sensible defaults because MOST PEOPLE HAVE NO BUSINESS RUNNING APPS THAT AREN'T VERIFIED. Macs ship with an option set in the Privacy & Security pane that limits apps to those from the App store -- but it's a radio button, and the other option is easy to choose ("App store and identified developers"). Yes, this still requires the code be signed, which is a 100% reasonable position in today's world. And yet: that's not even the end of it. If you do download something from an unsigned source -- either because it's built from source, or because it's from someone who is ideologically opposed to joining the dev program at Apple, or whatever -- all you have to do is right-click the icon and choose to open it. That will save it as an exception, and allow it to be run normally after that point. See: https://support.apple.com/guide/mac-help/open-a-mac-app-from-an-unidentified-developer-mh40616/mac https://support.apple.com/guide/mac-help/open-a-mac-app-from... At no point do you need to resort to "arcane shell commands" or "extended file system attributes." In fact, literally ALL of this is absolutely easy.