> For many apps the main source of memory usage isn't stack or heap memory consumed during runtime, it's the loading of the binary itself into memory.
Does iOS not do demand paging?
Does iOS not do demand paging?
While the process is active the whole binary is loaded (note: may not include dynamically linked libs, which is why that's a good idea - dylibs can be configured to load on-demand).
A triply-good reason why the pattern of "giant ball of statically linked things" is an anti-pattern.