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.
There are absolutely cases it’s worthwhile, but empirically the cutoff point leans more single threaded than most programmers think it does.
@Catfish_Man I tend to agree. Back in the day, we did not have threads and the scheduling entity was a process, and you only could do things through forks, and you could not take page faults above priority zero
@jeffmc oh interesting. That latter bit I hadn't heard, that's a fascinating restriction!
@Catfish_Man which meant if you took an interrupt in a device driver, scheduled a fork to run processing of the interrupt, all the code you ran had to be running in non-paged pool, because of that restriction.
@Catfish_Man in my experience, i’ve seen people drift to these things as a matter of processing many of the same/similar type of request when the concurrency component is not needed — wondering if there could be a new data structure for the purpose of uniformly processing items without the extra complexity
Follow friends and discover new ones. Publish anything you want: links, pictures, text, video. This server is run by the main developers of the Mastodon project. Everyone is welcome as long as you follow our code of conduct!