What's so hard about porting to a new hardware arch? Why would building for ARM Macs be any different than x86? Unless you have assembly code it's just a matter of changing a compiler flag, isn't it?
1. The x86 architecture gives programmers a lot of memory ordering guarantees, so that communication of values between threads does not usually need memory fences. ARM64 does not give so many guarantees, meaning that multi-threaded code may need additional memory fences to avoid data races. But data races due to out-of-order memory updates are hard to diagnose.
2. Page size in macOS is 4 kB on x86, but 16 kB on ARM, so if someone has hard-coded the page size rather than calling sysconf(_SC_PAGESIZE) this may need to be discovered and fixed.
https://stackoverflow.com/questions/62738652/gcc-turning-on-...
What is true is that if you want users to be able to just download and run (rather than download, run an obscure command, and then run your software), you have to pay Apple to notarize your builds.
Fuck Apple for this.
This also isn't true.
On a Mac (or on Windows) software that has not been digitally signed will show a scary dialog box telling you that software you download off the internet might be malicious.
On the Mac, to bypass this, you just right click the software and pick "Open".
xattr -rd com.apple.quarantine ~/Download/TheDamn.dmg