Sorry macOS users, but Apple has gone too far for some of us devs

So the major points are dropping 32bit support and Apple forcing you to sign your executable? The author claims that you need to pay Apple for the signing. as far as I know this is not true. You just need to pay for being on the application stores ...

Re: Sorry macOS users, but Apple has gone too far for some of us devs

#5

Post by dickeytk » Mon, Sep 30, 2019, 12:11 AM UTC

I’m glad Apple is locking down binaries. It’s terrifying what malicious binaries are capable of.

For games in particular there should be better sand boxing options.

Re: Sorry macOS users, but Apple has gone too far for some of us devs

#6

Post by dexter0 » Mon, Sep 30, 2019, 12:12 AM UTC

kgarten wrote: post #4

So the major points are dropping 32bit support and Apple forcing you to sign your executable? The author claims that you need to pay Apple for the signing. as far as I know this is not true. You just need to pay for being on the application stores ...

You have to pay the $99/yr to be in the developer program, to access to the notarization service.

Re: Sorry macOS users, but Apple has gone too far for some of us devs

#7

Post by atroche » Mon, Sep 30, 2019, 12:12 AM UTC

tmaly wrote: post #2

why is dropping 32-bit support even a consideration?

Maybe Cogmind depends on libraries which don’t support 64 bit? I agree though, it’s a bit weird. Maybe it’s harder for game-related libraries to switch, compared to the ones I’m used to using in my apps.

Re: Sorry macOS users, but Apple has gone too far for some of us devs

#8

Post by jayd16 » Mon, Sep 30, 2019, 12:13 AM UTC

kgarten wrote: post #4

So the major points are dropping 32bit support and Apple forcing you to sign your executable? The author claims that you need to pay Apple for the signing. as far as I know this is not true. You just need to pay for being on the application stores ...

If it's anything like iOS dev, you need Apple hardware to access the tools to sign your builds. You can't just run osx in a VM.

Re: Sorry macOS users, but Apple has gone too far for some of us devs

#9

Post by trothamel » Mon, Sep 30, 2019, 12:13 AM UTC

kgarten wrote: post #4

So the major points are dropping 32bit support and Apple forcing you to sign your executable? The author claims that you need to pay Apple for the signing. as far as I know this is not true. You just need to pay for being on the application stores ...

You have to pay for the signing. You also have to wait several minutes for the notarization process to finish, and submit every program to Apple.

Re: Sorry macOS users, but Apple has gone too far for some of us devs

#10

Post by rufius » Mon, Sep 30, 2019, 12:14 AM UTC

wjdp wrote: post #3

Does Apple have to sign games distributed through Steam? I thought that only applied to their own app store.

Mojave and Catalina added more restrictions around non-App Store programs where you need to sign and notarize.

I know I’ll probably catch downvotes for it but I think this is a good thing for the average user as someone in security. I know it makes it more of a walled garden but I also know that the harder it is to run untrusted code, the better for the average user.

The “terrible burden” is a couple of extra button clicks if working in Xcode or you could automate it with a script. I did the latter for the project I work on and it’s been fine.

That probably drives a lot of folks to Linux and that’s okay. I’m for diversity in platforms but I’m also for strong protections for the users.