Re: runOnMainQueueWithoutDeadlocking and all its evils.

2015-11-09 Thread Alex Zavatone
On Nov 6, 2015, at 1:23 PM, David Duncan wrote: > >> On Nov 6, 2015, at 8:36 AM, Alex Zavatone wrote: >> >> Bearing in mind my experience dealing with code in the past that was chock >> full of runOnMainQueueWithoutDeadlocking calls, I can not fathom why someone >> who was not updating the U

Re: runOnMainQueueWithoutDeadlocking and all its evils.

2015-11-09 Thread Alex Zavatone
On Nov 7, 2015, at 5:20 PM, Mike Abdullah wrote: > In my experience, the main issue is on OS X. If you ever display a modal > window, that runs the run loop in a special mode for the duration of the > window. The trouble is, that mode does not include dequeuing things from > GCD’s main queue,

Re: runOnMainQueueWithoutDeadlocking and all its evils.

2015-11-07 Thread Mike Abdullah
In my experience, the main issue is on OS X. If you ever display a modal window, that runs the run loop in a special mode for the duration of the window. The trouble is, that mode does not include dequeuing things from GCD’s main queue, so anything you ask to be done that way doesn’t happen. Fac

Re: runOnMainQueueWithoutDeadlocking and all its evils.

2015-11-06 Thread David Duncan
> On Nov 6, 2015, at 8:36 AM, Alex Zavatone wrote: > > Bearing in mind my experience dealing with code in the past that was chock > full of runOnMainQueueWithoutDeadlocking calls, I can not fathom why someone > who was not updating the UI would need to use this type of approach… > everywhere.

runOnMainQueueWithoutDeadlocking and all its evils.

2015-11-06 Thread Alex Zavatone
Bearing in mind my experience dealing with code in the past that was chock full of runOnMainQueueWithoutDeadlocking calls, I can not fathom why someone who was not updating the UI would need to use this type of approach… everywhere. Besides complete ineptitude, is there a rational reason that an