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.
-
-
FWIW I consider data-parallel stuff like this a somewhat separate problem domain. I agree it's often worth considering there.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
For sure, it makes still sense where there's a lot of opportunity for parallelism within the concurrent bits. I think
@Catfish_Man's point is geared more toward the higher-level UI event handling, that's generally less structured -
I mean, *my* perspective is mostly informed by daemons, so is possibly less useful than it seems ;) but yes, I think it's applicable here too
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.