4 ms·
I don’t necessarily mind paying the cost once but since I tend to refactor applications into multiple utility applications (separation of concerns, crash stabil
by makecheck 10y ago
I don’t necessarily mind paying the cost once but since I tend to refactor applications into multiple utility applications (separation of concerns, crash stability, security, etc.) this means each sub-bundle pays the cost too. At the moment I have not found an obvious way to avoid this, aside from somehow hacking all of them to symbolically-link to the same copy of the Swift libraries or something. Therefore, instead, I stick with Objective-C.