6 ms·
I only see two differences between MacOS and iOS: kernel development is allowed on MacOS, and running self-signed code doesn't delete itself even if you don't p
by ece 6y ago
I only see two differences between MacOS and iOS: kernel development is allowed on MacOS, and running self-signed code doesn't delete itself even if you don't pay like it does on iOS. Running unsigned code doesn't exist on MacOS anymore with Big Sur, unless you self-sign everything. Stop kernel development (going to be "higher friction" going forward) and a daemon to delete self-signed code, and it's iOS.
Allowing neutral parties to do app-signing for Chromebooks, Windows 10 S or i/MacOS (the way SSL-certs are issued and trusted by browsers, Mozilla App Store anyone?), alternative app stores (iOS), alternative signed-OSes on hardware (Occulus) are all Ulysses pacts that Apple, Google, Microsoft, Facebook and others could do.
- m463 6y agoI thought you could still disable stuff on macos and then run your own code to your heart's content. You know, boot into recovery and turn stuff off. Is that not true with Big Sur? On the other hand, there is no procedure like this on ios. I think you can run your own code, but you need an apple id (therefore apple's permission) and you can only run code for 7 days.
- Klonoar 6y agoYou can, even on the M1. It's more annoying now, sure, but still possible. Apple's been very clear that kernel extensions are going the way of the dodo, eventually, though - developers should be moving to DriverKit/etc. In truth, it's actually a better system. Slowly becoming more of a hybrid/micro kernel.