zlacker

> Then try to run it from the command line. Be told that it "cannot be opened because the developer cannot be verified". This is NOT the "is an app downloaded from the Internet, do you wish to run it?" dialog.

Yes, you get the “developer cannot be verified” error if the code isn’t signed. Which is perfectly fine, I don’t see how this is anti-consumer.

It’s $99 for a code signing cert (per developer account) on macOS/iOS, which I believe is less than what they cost on Windows.

>>sgjohn+(OP)
Yes, but the dialog doesn't tell you what to do if you do want to run the code. Why would I think that clicking "Open" in the popup menu would do anything different from double-clicking?

Also, an individual Microsoft Store cert is $19 (one-time, not per year), and a company account is $99.

>>gramie+Z1
So what? The average user is going to assume that it can’t be run (which is a good thing, as we don’t want people to run random unsigned binaries they find on the internet), and the tech-savvy ones will find a way.

It’s not like Apple is stopping you from running it. 1 quick google search and there you go. It’s a good design, in my opinion.

>>sgjohn+Mo1
> the tech-savvy ones will find a way

That doesn't sound like good design to me.

>>gramie+ok3
The average user has no need whatsoever to run unsigned code on macOS. Or on Windows for that matter, but code signing on Windows doesn't really matter as nobody reads those popups anyway.