zlacker

> Battery throtteling on the iPhone 6s

This is one of the ways I can tell what preconceived opinion someone has. The only problem with the battery throttling was PR. The engineering solution was correct and objectively better than not throttling. Should they have told users their battery was failing? Sure. But keeping the phone from crashing was better than letting it.

> unauthorized Apps on MacOS must be opened with a right-click

I've never had to do that.

>>rootus+(OP)
> I've never had to do that.

Using OKD (OpenShift Kubernetes Distribution) because I just dealt with this morning:

https://github.com/okd-project/okd/releases - download the MacOS installer and unzip it.

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.

Go to Finder, and double click it. Get the same message.

You have to go to Finder, then right click the app, specifically hit Open (which will open a terminal that will immediately exit), and only now can you run this app in your original terminal.

>>FireBe+Z8
> 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+WA
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.

>>FireBe+Z8
Interesting, thanks for the link. I've never run into that before. I've downloaded a lot of software, much of it open source. I've only downloaded from the Mac App Store maybe twice ever. But this is the first time I've gotten completely denied. Is it because it was a zip file with an executable inside, rather than an installer? Or as someone else mentioned, because it isn't signed at all? Are all the open source projects paying for signing certs for their OSX installer packages?

Again, thanks for the link. That's probably the only time I'll run into that, it clearly isn't my usual use case, but I'm glad you could back up the assertion with something I could see for myself.

I do agree that it should be clearer how you can run the executable if you really do trust it.

>>gramie+VC
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+IZ1
> the tech-savvy ones will find a way

That doesn't sound like good design to me.

>>gramie+kV3
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.