On Thu, Oct 3, 2013, at 12:14 PM, Jens Alfke wrote: > > On Oct 3, 2013, at 12:07 PM, Kyle Sluder <[email protected]> wrote: > > > They're fundamentally different ways of doing multiprocessing. > > So to use GCD I have to rip apart all of my code that uses > threads/runloops at once and rewrite it? (As I’ve said, I don’t mind > upgrading it bit by bit as I go; it’s the big-bang approach that scares > me.)
Carbon, anyone? > > > You _could_ have all your async queues target a serial queue that then > > enqueues a bunch of blocks on a specific thread, but why? > > I keep explaining this. So code that uses GCD APIs can coexist with code > that uses runloops. The "why" was a question of "Why go through all this effort to fight the framework, when the old way functions perfectly well?" What is adopting GCD going to get you if you aren't going to use GCD the way it was intended? --Kyle Sluder _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
