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.
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…
-
-
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.
-
I mean, before Vulkan, the APIs made you use one thread. Global hidden thread-specific mutable state ahoy!
- 4 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.