Comment on It's already running
Semi_Hemi_Demigod@lemmy.world 16 hours agoShh, don’t stop them when they’re acting superior
Comment on It's already running
Semi_Hemi_Demigod@lemmy.world 16 hours agoShh, don’t stop them when they’re acting superior
SnotFlickerman@lemmy.blahaj.zone 16 hours ago
The way macOS handles it is literally just exactly how Linux handles it. Makes sense considering macOS is certified UNIX and Linux is technically a re-implementation of UNIX.
TheTechnician27@lemmy.world 16 hours ago
turtlesareneat@piefed.ca 13 hours ago
You can certainly compile and run your own apps, you need to pay the developer fee if you want to distribute the software to other people’s Macs or iOS, or use advanced features like iCloud integration or push messages.
luciferofastora@feddit.org 7 hours ago
I think you missed the part where the common user won’t activate the scary feature that allows them to run arbitrary apps. You, as a dev, are in the minority. The point is that you could make a great app almost nobody would (be able to) use because you didn’t pay Apple to let them run it.
And push messages being an advanced feature is wild.
Semi_Hemi_Demigod@lemmy.world 16 hours ago
Well…
If you want to run a desktop app you need to have it signed or jump through a few minor hoops to grant it permission. (Go to system settings, authenticate, allow it, then right-click and select “Open”)
But it’s not like it’s impossible.
pivot_root@lemmy.world 14 hours ago
It’s not. They both expose a POSIX API and userspace, but the underlying architecture is very different. macOS is in part based on the Mach microkernel, and creating a process has a bunch of work related to that.
Even ignoring that difference, macOS has built-in signature checking that suspends a newly-started process the first time its executable is seen.