Programming Hot Take: named threads that you send runnables to (“*the* main thread”, “*the* I/O thread”, etc.) are equivalent to coarse-grained mutexes but worse in every way.
-
-
Replying to @xlerb
Further hot take: giving up on multi-threaded GUIs because it's hard is exactly as good an idea as all the other hard correctness things we've given up on.
1 reply 0 retweets 3 likes -
Well, before APIs like Vulkan, drawing commands pretty much had to be serialized. It’s interesting that Vulkan opens up the possibility of multithreaded UI rendering though…
1 reply 0 retweets 0 likes -
I think "drawing commands have to be serialized" is a constraint similar to "writes to a specific file have to be serialized". But if Oracle made you use "the DB thread" that would be ridiculous. Obviously writing a multi-threaded GUI isn't easy, but many things are hard.
2 replies 0 retweets 1 like -
I mean, before Vulkan, the APIs made you use one thread. Global hidden thread-specific mutable state ahoy!
1 reply 0 retweets 0 likes -
Right, that's just the same problem (some combination of "it's too hard" and "640k is good enough for anyone") at the next level down.
1 reply 0 retweets 0 likes -
But we have Vulkan now! So it would be interesting to have a toolkit that does multithreaded UI drawing.
1 reply 0 retweets 0 likes
Multithreaded UI rendering on GPU strikes me as a perfect topic for someone in academia to try, incidentally.
-
-
cc
@johnregehr — you might be interested too0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.