3 ms·

I‘m intrigued where you got that info. As an iOS dev, I can tell you that an app should not access UIKit stuff off-main-thread. Facebook does off-main-thread la

by manmal 9y ago

I‘m intrigued where you got that info. As an iOS dev, I can tell you that an app should not access UIKit stuff off-main-thread. Facebook does off-main-thread layouts [1], but they still rely on backing views on main thread. Or do you mean that the rendering/compositing itself is multithreaded? [1]: https://code.facebook.com/posts/721586784561674/introducing-asyncdisplaykit-for-smooth-and-responsive-apps-on-ios/ https://code.facebook.com/posts/721586784561674/introducing-...

aphextron 9y ago
>I‘m intrigued where you got that info. As an iOS dev, I can tell you that an app should not access UIKit stuff off-main-thread. Facebook does off-main-thread layouts [1], but they still rely on backing views on main thread. Right, I wasn't implying UIKit stuff is done multi threaded. I just meant that the best practice is to do all your UI work in the main thread, and use GCD for any blocking operations which shouldn't be on the main (animation) thread.