Dynamic Linking Is Bad For Apps And Static Linking Is Also Bad For Apps
Summary
A recent question on the Swift forums prompted me to actually write this blog post I’ve been idly thinking about for a long time. It can even be used to replace a dependency, say, with a version of a library that does extra checks for debugging purposes, or one from a different vendor that provides a compatible implementation of the public interface. Both of these use only a subset of the libraries that the main app uses, and indeed iOS requires that with strict limits on processing time and memory usage. What I want is a format that behaves like an object file or static library, but which has already gone through a round of linking: deduplication, removing non-public symbols, dead-code stripping, maybe even some link-time optimizationwant. But many environments work around that by putting in extra metadata, such as Swift’s “autolinking” info, so I didn’t include it as a format drawback above.
Classifications
AskAI Classifications
LabelsLinked Companies
