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.
-
-
They were doing something right; the consistent responsiveness of the UI was pretty remarkable for 90s era single-core hardware, even if throughput was bad
-
One-thread-per-window, not per-widget; the latter would indeed be silly. But yes, BeOS was surprisingly responsive with this model; its kernel was "fully SMP-ready" before Linux or *BSD even began thinking about how to remove the giant lock.
End of conversation
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.