5 ms·
Yikes. If you can't figure out how to make your code 64-bit safe, or how to make code signing work, you are effective requiring your users to give you root acce
by gok 7y ago
Yikes. If you can't figure out how to make your code 64-bit safe, or how to make code signing work, you are effective requiring your users to give you root access. Completely unacceptable for a game.
- delfinom 7y ago> you are effective requiring your users to give you root access Wait, it's either code sign and you don't get root or don't code sign and get root? How retarded is macOS? Why is there no "no code sign and no root, just run as the user"?
- povertyworld 7y agoI'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?
- op00to 7y agoPlease don’t use that term in the way you’re using it. It’s offensive and unnecessary.
- povertyworld 7y agoI'm quoting the guy above me. Go tell him.
- lonelappde 7y agoTwo wrongs don't make a right.
- iliketocomplain 7y agoWhat?
- crooked-v 7y agoPlenty of coding practices from 1999 are completely unacceptable today.
- povertyworld 7y agoYes. That is why Apple requires you to get your code signed.
- olliej 7y agoOr: you don’t codesign and users ignore your app in favor of the one that doesn’t require rebooting to recovery mode to disable core platform security features, so that chrome, etc can break your machine. Longer term I imagine that OS X will simply have an non-overridable sandbox that tightly restricts what any unnotarized app can do. Eg if you aren’t notarized you get access to your own container and no other part of the file system. Alternatively you could just sign your code properly and update it to hardware that’s existed for 15 years.
- judge2020 7y agoAnalogy falls apart for Chrome since it's safe to assume Apple either gives scaning priority to Google or has outright whitelisted their account (since Chrome updates so frequently and there's opportunity for Google to throw money at Apple)
- rcruzeiro 7y agoDoes chrome releases multiple builds a day? Scanning usually takes less than 1 hour.
- olliej 7y agoNotarization takes minutes and is presumably automated, so why wouldn’t chrome do it? You’re doing a great disservice to the engineers at google if you think the actual release work is so short that a few minutes for notarization is a problem.
- gridspy 7y ago1. You also need to pay apple a subscription, update your hardware, change your build process. I think there is also a review step during the build. 2. All the existing tooling (not the game, but the build process) will need to be 64 bit to run on this new hardware. So the build needs to be re-worked 3. People on Mac require more support, which is harder because dev is not a Mac user.
- deleted 7y ago[deleted]
- povertyworld 7y agoDo these guys complain this much about releasing games on consoles too?
- Aeolun 7y agoThat’s a fundamentally different platform I think.
- yjftsjthsd-h 7y agoIn some ways, it isn't that different; consoles are just computers with some platform-weirdness. But I do actually agree insofar as that I can reasonably target NT, Darwin, and Linux from one machine (so long as it's a mac or I'm willing to break the Apple EULA), but to target consoles, so far as I know, requires purchasing additional hardware.
- Nullabillity 7y agoProbably, consoles aren't mentioned at all in the blog post or on the game's website.
- smileybarry 7y agoIronically, releasing on consoles got easier over the years. Patch certification cost (and possibly the entire requirement for indies) got dropped and programs like ID@Xbox allow you to release your game for free.
- Aeolun 7y agoIsn’t this every game ever until a few years ago? The only OS where I’ve ever been bothered by ‘this code isn’t signed’ has been OSX.
- pippy 7y agoCompletely agree. The developer account is a great way to disincentive malicious apps from being made. I would accept the following for not supporting MacOS: * lack of vulkan support * porting code to the apple SDK * cost/benefit for small indie titles pointing out how many people logged bugs doesn't mean that the OS is buggy. it simply means you've written shitty code. Another odd point with OP is that he's made the effort to start supporting it. Dropping support is always more expensive than simply fixing some issues, as you've already made the investment. Most developers seem to have rational decisions behind their support. This post seems like they're jumping on the Apple hate bandwagon.
- rkachowski 7y agoIn what way is lack of 64 bit support + lack of code signing equal to elevated permissions?