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.
I mean, before Vulkan, the APIs made you use one thread. Global hidden thread-specific mutable state ahoy!
-
-
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.
-
But we have Vulkan now! So it would be interesting to have a toolkit that does multithreaded UI drawing.
- 2 more replies
New conversation -
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.