You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
Hugo Melder
hmelder
Computer Science @ Technical University of Munich (TUM)
After installing mitmproxy run it (just type mitmproxy) in a terminal session and quit.
This will create the necessaries certificates files at ~/.mitmproxy.
Extract the certificate to .crt format: openssl x509 -in ~/.mitmproxy/mitmproxy-ca.pem -inform PEM -out ca.crt
Trust the certificate into CA: sudo trust anchor ca.crt
The libdispatch is one of the most misused API due to the way it was presented to us when it was introduced and for many years after that, and due to the confusing documentation and API. This page is a compilation of important things to know if you're going to use this library. Many references are available at the end of this document pointing to comments from Apple's very own libdispatch maintainer (Pierre Habouzit).
My take-aways are:
You should create very few, long-lived, well-defined queues. These queues should be seen as execution contexts in your program (gui, background work, ...) that benefit from executing in parallel. An important thing to note is that if these queues are all active at once, you will get as many threads running. In most apps, you probably do not need to create more than 3 or 4 queues.
Go serial first, and as you find performance bottle necks, measure why, and if concurrency helps, apply with care, always validating under system pressure. Reuse
Find the docset you want (there are some with URL https://apple.com/none.dmg; ignore them - you will find them again further down the file with a working URL).
Download the dmg. It's probably around a gigabyte or so.
"Install" the .pkg file somewhere on your disk. If you don't trust the installer, do it manually:
Find the largest file, named Payload, and extract it using The Unarchiver.
This creates a new, even larger file, probably named Payload-1.
Extract Payload-1 using The Unarchiver.
After many minutes of extracting, we have our .docset file.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters