Comment by toyg
4 years ago
First they restricted execution of unsigned binaries unless you run in a substantially-unprotected mode: https://github.molgen.mpg.de/pages/bs/macOSnotes/mac/mac_pro...
Then they disabled execution of all unsigned binaries. To run on a default Mac, you either pay Apple or compile on the user's own machine which is obviously unsustainable. https://eclecticlight.co/2020/08/22/apple-silicon-macs-will-...
They've also removed any 32bit support, in case you could make do with old programs that don't make Apple some money.
I'm still on Mojave and will not upgrade. Personally, my last MBP was bought in 2016 and I have no intention of getting another one as long as they continue exploiting developers and the public in this way.
> To run on a default Mac, you either pay Apple or compile on the user's own machine
This is not true. Apple silicon runs code with any signature, even an ad-hoc one.
What exactly do you mean ad-hoc? Can my friend without an apple account compile an executable with GCC send it to me and I can run it on my new Apple Macbook?