41–50 of 118 posts
Earlier quoted context omitted.
> 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"?
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?
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.
Earlier quoted context omitted.
> 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"?
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?
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.
Earlier quoted context omitted.
> 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"?
Or: 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 o…
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?
Plenty of coding practices from 1999 are completely unacceptable today.
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.
1. 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.
the first commercial downloadable game I released back in 2015, that let me become a full-time indie developer, has done roughly 25% of its revenue over the last four years on Mac. This is adding together the % of copies sold on Steam for Mac users, and the Apple Mac Store, where my game was featured on the main page for three months. Notarization, and 64-bit support, and all that aside, the audience on Mac that you…
Earlier quoted context omitted.
All malware checkers must read the app binary to be effective. Apple forces the app to be scanned once, not one million times on one million desktops.
Apple also forces every single app for macOS to be submitted to them. Seeing as how Apple has historically been willing to compete with the applications on their platform, that seems to at least have the potential to be a problem.
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.
Our OSes all date back to a time when security simply was not such a concern. All binaries almost have root. A modern OS would be least-privilege all the way.
Btw web browsers show that it is possible to run untrusted code locally in a sandbox and do so fairly safely.