Apple would surely impose the same level of lockdown on MacOS if they thought they could get away with it - but it would not be accepted by Mac "power users" and developers - at least for Mac OS apps. Think about it - an iPad or iPhone are locked down to the equivalent of the highest MacOS security level, with no option to turn it off (without an unofficial jailbreak). If we're talking about turning off secure boot ans OS signing then disabling iOS is probably by design and any fix may be limited to a suitable "here be dragons" warning, if there aren't already enough when you switch to reduced security.
CDOCK N TALK FULL
It also suggests that the command-line CSRUtil enables finer control (.but I couldn't find full docs - the pre-M1 version just seems to turn SIP on/off). my reading of that is that "reduced security mode" disables a raft of security features including "secure boot" and enables booting of unsigned OSs (the video doesn't mention SIP at that point). So, yeah, the Intel Macs (up until the introduction of the T2) were arguably closer to "Wintel PCs" than ever before or since.
CDOCK N TALK SOFTWARE
The flipside of that is that Intel-era MacOS is able to run on carefully-selected, but generic, "Wintel PC" hardware with only superficial (but clever - kudos to the Hackintosh community) software hacks.
CDOCK N TALK INSTALL
let's call it generic "Wintel PC" hardware that you could just stick in a regular Windows (or PC Linux) installation DVD into some Mac models, install it and have it run tolerably well with just the generic or downloaded 3rd party drivers (I've done that on the original Mac Pro with Windows XP). What is true is that Intel era Macs have, at times, been so close to. Macs have never been strictly MacOS, though - Apple offered their own (pre-MacOS X) Unix (A/UX) for a while and there were Linux distros - such as Yellow Dog - that ran bare-metal on PPC Macs, and BeOS was around for a while. (MacOS has unofficially run on things like the Atari ST and Amiga in the past, albeit with hardware hacks). and (outside of the abortive era of official Mac clones) only Mac-branded machines can officially run MacOS, which is sometimes a matter of technology, sometimes simply licensing.
The only solid definition of Mac/Macintosh is that it is a trademark of Apple inc. But then there's "PowerPC", "PCMCIA" and numerous products with names of the form "Whizzbang PC1701D". Before that, articles tended to either use "personal computer" in full or "micro" (short for "microcomputer" and/or "microprocessor"). NB: I've previously dug out old computer magazines pre-1981 and while "Personal computer" definitely pre-dates IBM (heck, one of the magazines was called "Personal Computer World") and the abbreviation "PC" wasn't entirely unknown, it was pretty clear that it was the IBM PC that established "PC" as a household pseudo-brand name.
a large, red juicy but rather flavourless US variety of eating apple. Meanwhile, I await the first comparative review of the new MacBook Air vs. I guess some people really can't deal with the idea that language is ambiguous and context matters. and the wikipedia article also mentions the dispute between "experts" on what a PC means. One can hope.īut, to expect EVERYTHING to operate "smooth as butter" on day 1 of a brand new release of Big Sur (11.0.1) on a completely new platform (M1 Macs), is expecting a bit much, methinks. If this is the case, it's just a matter of time before Apple addresses this fragility, and disabling SIP won't cause this collapse. You're freaking out the SIP Daycare Worker! "The iOS children are running amok! AAAAAAAAH!" ? If iOS apps are running inside a SIP "sandbox", of sorts, it's any wonder disabling it is causing this problem. Disabling SIP just throws a massive wrench into the newly installed gears (for running iOS apps) of Big Sur and this fragile process "freaks out". If iOS apps have never been able to run on Big Sur (or earlier), this makes a lot more sense. Perhaps the reason disabling SIP causes iOS apps to not work, is because the system throws a "red flag" after disabling SIP, which then causes all "beta type features" (this is the first release of 11.0.x for M1 Macs) to stop functioning. SIP is designed to protect the system (System Integrity Protection), as explained on the osxdaily link. Click to expand.From what little research I've just done (going to the cDock github page), it appears to me that cDock is a "hack".