Live data from Hacker News

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

gridsagegames.com

91–100 of 118 posts

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

#91
post #41

Earlier quoted context omitted.

I'm pretty sure on Linux if you wanted to run Quake3 you had to run as root due to needing direct access to the GPU. Is Linux "retarded" too?

Please don’t use that term in the way you’re using it. It’s offensive and unnecessary.

What?

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

#92
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.

Notarization is free and in my experience it can take as little as 60 seconds for it to complete.

https://developer.apple.com/documentation/security/notarizin...

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

#93
post #22
post #10

Earlier quoted context omitted.

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…

Letting megacorporations decide what you do and do not get to do with your personal property isn't really what I would count as a "good thing" in any circumstance. Apple has gotten away with eliminating user freedoms time and time again under the guise of security. In many scenarios Apple's attitude towards its end-users increases perceived security while causing significant hurdles for actual security, such as how i…

Don't buy a Mac then. It's not like they're forcing you.

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

#94

As someone who recently worked in game dev I'm not sure why 32 bit was even a factor as 64 bit is likely your default target anyway - has been for awhile. So, killing 32 bit is not a real issue. Notorizing can be seen as just another cost of targeting a platform. So do it. You will need at least one machine anyway to do basic testing on. So use that. Get the cheapest imac or whatever you require. So, mac hardware isn…

What surprises me is the fact that the author doesn't talk about the craziest of Apple's recent choices: the deprecation of OpenGL. This is much worse than the deprecation of 32 bit and, IMHO, it's just Apple giving up on being a relevant gaming platform. This, plus the lack of nvidia drivers and of support for Vulkan.

All the small issues here show, together, that indeed Apple doesn't give a shit about gaming and about interoperability with other platforms. They want developers to be faithful to their locked garden and their technologies.

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

#95

Earlier quoted context omitted.

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.

Notarization is free and in my experience it can take as little as 60 seconds for it to complete. https://developer.apple.com/documentation/security/notarizin...

I assumed you need to be in "Apple Developer Program" to notarize apps.

https://developer.apple.com/documentation/security/notarizin...

https://developer.apple.com/support/developer-id/

https://developer.apple.com/support/compare-memberships/

https://developer.apple.com/support/roles/

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

#96
post #56

Earlier quoted context omitted.

> It’s not burdensome As defined by who? 1. Submit build 2. Wait an hour 3. Retrieve notary receipt 4. Staple to correct build 5. Upload build Sure sounds more burdensome to me than: 1. Upload build Edit: Lol, people arguing with reality. It may or may not be a good thing, but arguing that it doesn’t add any burden to the developer seems hard to me.

Wouldn't you have jenkins (or whatever your build system is) do that all for you?

Possibly, but even modifying your Jenkins script is a ‘burden’. Apparently their polling mechanism also makes that a bit painful.

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

#97
post #64

Earlier quoted context omitted.

I imagine Steam doesn't allow Gatekeeper bypasses. Still, notarization is designed to be easy to script: https://developer.apple.com/documentation/xcode/notarizing_y... - so it really shouldn't be an issue.

The only issue is it can take an hour or more - https://news.ycombinator.com/item?id=21110622 polling for the status to finalize would waste build minutes on your CI.

My limited experience notarizing a hello world react electron app took 10 to 15 minutes. Not that much but a large increase from the 1 minute build time before

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

#98
post #56

Earlier quoted context omitted.

The developer has every right to support or abandon whatever platforms they want. But there’s some FUD here: 1. There is no review step. Notarization is an automated process that takes about an hour. It doesn’t require a substantive change to your build process. You just submit your build, get a notary receipt file back from Apple about an hour later, and “staple” it to your build using a single tool. It’s not burden…

> It’s not burdensome As defined by who? 1. Submit build 2. Wait an hour 3. Retrieve notary receipt 4. Staple to correct build 5. Upload build Sure sounds more burdensome to me than: 1. Upload build Edit: Lol, people arguing with reality. It may or may not be a good thing, but arguing that it doesn’t add any burden to the developer seems hard to me.

You know what's also a burden? Writing a good game. So I'll just write a shitty one to decrease burden.

Isn't burden the thing you're actually getting paid for when you sell the game?

If adding 2 steps to your build process is such a burden that it results in you not supporting an entire platform, you're either lazy or looking for an excuse.

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

#99
As an active Apple dev with five commercial apps, I agree with the sentiment in the article. I'm ready to leave Apple the moment something better comes along.

Since Steve died, every decision at Apple has been anti-dev and anti-user.

The price/performance of the hardware is awful. Apple is the current tech leader in planned obsolescence. Old hardware is iCloud locked by default with no option to contact the registered owner to tell them that they forgot to unlock it. Now they want to extend that practice to laptops. The developer documentation is universally awful. The version changes in Swift are so drastic and frequent that you can't find solutions for the current version because the Internet is polluted with information about previous versions. They are glacially slow to fix bugs. They have removed basic networking functionality covered in the RFCs. They instantly kill backgrounded apps in a mad race for style over function.

I. Could. Go. On.

TL;dr I hate Apple with a burning passion and only inertia keeps me in the Apple dev world.

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

#100
post #22
post #10

Earlier quoted context omitted.

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…

Letting megacorporations decide what you do and do not get to do with your personal property isn't really what I would count as a "good thing" in any circumstance. Apple has gotten away with eliminating user freedoms time and time again under the guise of security. In many scenarios Apple's attitude towards its end-users increases perceived security while causing significant hurdles for actual security, such as how i…

Sorry, but this reads like "the seatbelt and airbag in my car prevent me from fully utilizing my personal property".

For 99,99% of users, notarized apps are a positive. For the 0,01% who need it disabled, press the CTRL button.

Post reply on HN