btw on the subject of “should I use NSOperationQueue or libdispatch”, since it came up, my concrete recommendation is: you should really strongly consider not writing async/concurrent code. I know this sounds weird in 2018, but the cost in complexity *and* performance is high.
-
-
(BTW, browsers—including Safari, via libdispatch—all use multithreaded vector graphics on a tiled basis now. Quite nice speedup.)
-
FWIW I consider data-parallel stuff like this a somewhat separate problem domain. I agree it's often worth considering there.
End of conversation
New conversation -
-
-
BeOS went all in on kernel threads and one-thread-per-window/runloop/widget, which IIRC forced a lot of synchronization overhead even with their fancy scheduler
-
Oh, well, that’s obviously silly then :)
- 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.