MacOS Catalina: Slow by Design?
sigpipe.macromates.com
MacOS Catalina: Slow by Design?
1–10 of 1001 posts
Re: MacOS Catalina: Slow by Design?
#2> This is not just for files downloaded from the internet, nor is it only when you launch them via Finder, this is everything. So even if you write a one line shell script and run it in a terminal, you will get a delay!
> Apple’s most recent OS where it appears that low-level system API such as exec and getxattr now do synchronous network activity before returning to the caller.
Can anyone confirm this? Because honestly this is just terrifying. I don't think even Windows authorises every process from a server. This doesn't sound good for both privacy and speed.
Re: MacOS Catalina: Slow by Design?
#3If Microsoft wasn't doing ever worse privacy things with Windows I'd seriously look into switching away from Mac OS given the ever growing issues it's been having with every release.
Re: MacOS Catalina: Slow by Design?
#4> This is not just for files downloaded from the internet, nor is it only when you launch them via Finder, this is everything. So even if you write a one line shell script and run it in a terminal, you will get a delay! > Apple’s most recent OS where it appears that low-level system API such as exec and getxattr now do synchronous network activity before returning to the caller. Can anyone confirm this? Because hones…
Privacy it may be a plus since in theory notarization provides some protection.
Speed, definitely not, this is going to make things slowwwww
Re: MacOS Catalina: Slow by Design?
#5> a degraded user experience, as the first time a user runs a new executable, Apple delays execution while waiting for a reply from their server.
The way to avoid this behavior is to staple the notarization ticket to your bundle (or dmg/pkg), i.e. "/usr/bin/stapler staple ." Otherwise, Gatekeeper will fetch the ticket and staple it for the user on the first run.
(I'm the author of xcnotary [1], a tool to make notarization way less painful, including uploading to Apple/polling for completion/stapling/troubleshooting various code signing issues.)
Re: MacOS Catalina: Slow by Design?
#6I can't upgrade IntelliJ any more, because it's trying to write to privileged file locations that I (the owner of the computer) no longer have access to. Believe me, I've tried to work around this, macOS has it locked down completely.
Re: MacOS Catalina: Slow by Design?
#7I can't upgrade IntelliJ any more, because it's trying to write to privileged file locations that I (the owner of the computer) no longer have access to. Believe me, I've tried to work around this, macOS has it locked down completely.
You can disable SIP in recovery mode.
Re: MacOS Catalina: Slow by Design?
#8> This is not just for files downloaded from the internet, nor is it only when you launch them via Finder, this is everything. So even if you write a one line shell script and run it in a terminal, you will get a delay! > Apple’s most recent OS where it appears that low-level system API such as exec and getxattr now do synchronous network activity before returning to the caller. Can anyone confirm this? Because hones…
Privacy it may be a plus since in theory notarization provides some protection. Speed, definitely not, this is going to make things slowwwww
> provides some protection.
That's security, not privacy...
Re: MacOS Catalina: Slow by Design?
#9If Microsoft wasn't doing ever worse privacy things with Windows I'd seriously look into switching away from Mac OS given the ever growing issues it's been having with every release.
The set of possible operating systems to consider does not contain two items.
Re: MacOS Catalina: Slow by Design?
#10Reminds me of the terrible delay I faced after having Sophos installed on my Mac.
Having to wait 5-10 seconds for a new terminal tab as Sophos churns (checking autoccomplete scripts, rbenv, etc) was infuriating. Oddly, there was fate sharing with Internet interception, so there was a good chance the browser was getting dragged down too, and vice versa.
Convincing corporate IT of how bad the problem was was maddening. Based on what this author says, 10.15 on rural internet sounds like hell.