News for hackers. Stuff that matters.
Re:Multithreaded toolkits: A failed dream? (2004) by wrl on Monday November 02, 2015 @04:19AM (#10490832)
A big reason why multithreaded UI doesn't work is that the platform code (win32, cocoa) generally has poor support for interacting with OS objects from multiple threads. For instance, NSView instances can only be operated on from the main thread (https://developer.apple.com/library/mac/documentation/Cocoa/...).

Handling OpenGL context access from multiple threads is terrible, too. I'm quite excited about the additional threading niceties that we're getting in Vulkan, which should allow separate threads to re-render parts of the UI and then send the command buffers back to the main thread.

Re:Multithreaded toolkits: A failed dream? (2004) by mpweiher on Monday November 02, 2015 @04:37AM (#10490876)
> For instance, NSView instances can only be operated on from the main thread

Cocoa is the toolkit, not the OS, so this is just Cocoa taking exactly the approach described in the fine article.

Re:Multithreaded toolkits: A failed dream? (2004) by wrl on Monday November 02, 2015 @07:59AM (#10491563)
It's also an unavoidable part of writing graphical code on OS X, so, for all intents and purposes, it is the OS.