Point 22 in the linked article confuses static linking against the C runtime with static linking against your own libraries. It is perfectly all right on macOS

Point 22 in the linked article confuses static linking against the C runtime with static linking against your own libraries. It is perfectly all right on macOS to statically link your own stuff, or other peoples' stuff. Apple even recommend in a WWDC video that you do it with OpenSSL if you absolutely must use that instead of the framework they provide. (The stated reason is that the OpenSSL API is not stable.) Like almost every other system except for Linux, it is not perfectly all right to statically link against the C runtime, because that’s what knows how to do system calls. But neither is it ever a problem to dynamically link against it, since it will be kept up to date by system updates. Any normal C++ program will dynamically link against libc++ and libSystem in /usr/lib. Apple packages its APIs as "Frameworks", and a normal application will dynamically link against those.