The Gates to Hell: Apple’s Notarizing
cdfinder.de
The Gates to Hell: Apple’s Notarizing
1–10 of 214 posts
Re: The Gates to Hell: Apple’s Notarizing
#2Apple devices are becoming increasingly unusable for developers.
Fantastic opportunity for Linux apps to gain more dev resources, as anyone with a bit of foresight sees little future in macOS, iOS, Windows, or Android as development platforms.
Re: The Gates to Hell: Apple’s Notarizing
#3If you're going to rant about details, it helps to actually get the details right.
For example, showing a screenshot that doesn't contain the word "malware" and then saying:
> Using my application name and the word "malware" in one sentence is suggestive and extremely offensive by Apple.
Does not fill me with much hope that the author is detail-oriented. I'll keep reading, and I know already that the notarizing process isn't smooth, but my "snowflake meter" is already in the yellow zone, and I've yet to reach the part of the essay labeled "Part 1"
Re: The Gates to Hell: Apple’s Notarizing
#4Maybe Apple should hire Steve Ballmer, I hear he's available: https://www.youtube.com/watch?v=OHVhiybBb1U
Re: The Gates to Hell: Apple’s Notarizing
#5Apple devices are becoming increasingly unusable for developers. Fantastic opportunity for Linux apps to gain more dev resources, as anyone with a bit of foresight sees little future in macOS, iOS, Windows, or Android as development platforms.
I personally gave up, I treat all of their platforms as "legacy" and only port stuff as "best effort" similar to what I was doing with IE in the IE days (yes, that also includes Safari).
Re: The Gates to Hell: Apple’s Notarizing
#6If you're going to rant about details, it helps to actually get the details right. For example, showing a screenshot that doesn't contain the word "malware" and then saying: > Using my application name and the word "malware" in one sentence is suggestive and extremely offensive by Apple. Does not fill me with much hope that the author is detail-oriented. I'll keep reading, and I know already that the notarizing proce…
Is the difference between "malware" and "malicious software" really that meaningful that it undermines the overall point of the piece?
Re: The Gates to Hell: Apple’s Notarizing
#7Notarization has been a nightmare of a solution to a problem that isn't effective. You can get practically as much security by pushing malware signatures to the client without the massive privacy overreach of having Apple archive each and every bit of code that you generate for distribution.
This is just Apple's overreach extended to the desktop. Excessive control that makes developer's lives hell while adding barely any security on top.
Re: The Gates to Hell: Apple’s Notarizing
#810.15 was released 18 months ago so I assume this article is from 2020.
The process has improved since then so not sure how much of this still applies.
Re: The Gates to Hell: Apple’s Notarizing
#9If you're going to rant about details, it helps to actually get the details right. For example, showing a screenshot that doesn't contain the word "malware" and then saying: > Using my application name and the word "malware" in one sentence is suggestive and extremely offensive by Apple. Does not fill me with much hope that the author is detail-oriented. I'll keep reading, and I know already that the notarizing proce…
It’s a fair point, though the dialog I usually see says “macOS cannot verify that this app is free of malware”. Presumably that’s because Apple scans the uploaded executable for malware during notorization.
Re: The Gates to Hell: Apple’s Notarizing
#10Apple devices are becoming increasingly unusable for developers. Fantastic opportunity for Linux apps to gain more dev resources, as anyone with a bit of foresight sees little future in macOS, iOS, Windows, or Android as development platforms.
I personally gave up, I treat all of their platforms as "legacy" and only port stuff as "best effort" similar to what I was doing with IE in the IE days (yes, that also includes Safari).
Recently getting into web development, getting things to look right on Safari has been such a pain... they really just work on Firefox and Chrome, but every time we deploy a new version, the one coworker with a Mac will message us about some arcane difference in behavior for certain CSS we're using on Safari.
I wish we could drop it, but our Analytics disagree, sadly.