←back to thread

MacOS Catalina: Slow by Design?

(sigpipe.macromates.com)
2031 points jrk | 4 comments | 22 May 20 15:39 UTC | HN request time: 0.001s | source
Show context
davidvartan ◴[22 May 20 15:53 UTC] No.23273396[source]▶
> 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 <path>." 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.)

[1] https://github.com/akeru-inc/xcnotary

replies(5): >>23273530 #>>23273867 #>>23273940 #>>23275792 #>>23279360 #
oefrha ◴[22 May 20 16:04 UTC] No.23273530[source]▶
I mean, when I’m developing in a compiled language with the workflow edit code -> compile -> run (with forced stapling), changing it to edit code -> compile -> staple -> run doesn’t make it any less slow...
replies(2): >>23273583 #>>23274903 #
1. davidvartan ◴[22 May 20 16:07 UTC] No.23273583[source]▶
Notarization/stapling/etc. is for distribution only, not generally part of your dev workflow.
replies(2): >>23273609 #>>23273823 #
2. oefrha ◴[22 May 20 16:10 UTC] No.23273609[source]▶
But TFA and my personal experience do point to a noticeable delay after each recompile in dev workflows, and TFA claims this is due to notarization checks... So I guess I’m confused and you’re talking about something else?
3. rgrs ◴[22 May 20 16:27 UTC] No.23273823[source]▶
How does mac identify a dev workflow and normal workflow?
replies(1): >>23273888 #
4. jmercouris ◴[22 May 20 16:32 UTC] No.23273888[source]▶
When you use XCode you have different compilation options.