3 ms·
I sometimes wonder what the IT world would look like if IBM locked down their IBM PC as hard as Apple currently does with their offerings.
by amelius 3y ago
I sometimes wonder what the IT world would look like if IBM locked down their IBM PC as hard as Apple currently does with their offerings.
- ubermonkey 3y agoPresumably 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 agomacOS 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 agomacOS 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 agoI 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.
- fch42 3y agoIt'd look exactly the same, because been-there-done-that. IBM went that way with the PS/2 systems - microchannel, 8514 graphics, supported my IBM PC-DOS (and OS/2, and IBM-OEM'ed Windows). IBM before that had the BIOS lawsuit against Compaq (https://www.allaboutcircuits.com/news/how-compaqs-clone-computers-skirted-ibms-patents-and-gave-rise-to-eisa/ https://www.allaboutcircuits.com/news/how-compaqs-clone-comp...) attempting to defend their market ownership; PS/2 came after in the attempt to "re-corner" the market in a way one would today call "Apple style" (walled garden proprietary HW/SW). Too late though. But not for lack of want on IBM's side.
- timbit42 3y agoI think the question was if the original IBM PC in 1981 had been locked down such that the BIOS couldn't be cloned.
- timbit42 3y agoIf the IBM PC hardware (and PC/MS-DOS) was locked down, it would have lost its advantage and would have had equal footing with the alternatives, the Apple Macintosh, the Atari ST, the Commodore Amiga and the Acorn Archimedes, all of which were also locked down. CP/M (or MP/M) and GEM could run on hardware that wasn't locked down so perhaps some 16-bit version of that could have replaced the 8-bit versions of CP/M and that hardware could have become an open standard.