> if you don't like the "walled garden" approach you shouldn't be using Apple
But I use none of Apple's online services. Not even the app store. App store for me is the place to update Apple apps, and that's really it.
> and if your complaint is paying to have your code signed properly as a dev, that's the same across macOS and Windows,
Windows? I know you can sign Windows executables, but why would anyone want to? I have Windows 11 on a VM. It runs unsigned executables just fine and, unlike macOS, doesn't treat them like they're radioactive. You just get a differently-colored confirmation window if you run them as administrator.
> in a similar vein to SSL certs for websites
And before Let's Encrypt and other similar free automatic CAs came along, SSL/TLS was very niche.
See, it's about choice. If you want to throw your money away for some reason, sure you can still pay for an SSL certificate. Or you can use Let's Encrypt for free, set it up once and forget. Your users would see a lock icon either way. No such luck with macOS app signing — Apple is your only option.
I like Android's security model better. You sign your apk with a self-signed certificate. No signing identity is enforced upon initial installation, but if you release an update, the new apk has to be signed with the same certificate. You can install an apk with the same package id but a different signature only after you uninstall the previous one (and delete all its private data). This helps with security and data integrity. I see no reason why Apple couldn't adopt a similar scheme on their platforms, except that they want all control they could get away with.