I think what I love the most about scale is that I can sit down for a couple hours and write a five-line patch that will, when taken in aggregate, save many lifetimes of waiting for things to load
By the way, if you’re using method_setImplementation/method_exchangeImplementations in your app, you may wish to reconsider doing so if possible for performance reasons. (If you’re using them to swizzle, there might be correctness reasons as well–but I digress.)
In particular, Methods don’t keep a backpointer to which Class they come from. This means that using either of those two functions means that the Objective-C runtime needs to blow out the method cache for *all* classes–potentially tens of thousands of them in a large app.
It’s often that case that you know which Class you are targeting–if so, try using class_replaceMethod instead. If used correctly, it works like method_setImplementation but lets you specify the class as a parameter, allowing the runtime to only have to flush caches on that class.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
