[coldcode]

I don't find GCD difficult to write for, maybe if you are used to Go it is different enough. Not sure what exactly you would use Go for in an iOS/Macos app unless maybe you have a Go framework you want to include.

[saagarjha]

Isn’t this what the author is doing?

[mmjaa]

I consider GCD to be a bit of a smell - not because its difficult to write for, but rather because its difficult to port such code elsewhere. And really, this seems to be the only rationale for Apple having maintained it as a component of the architecture for iOS - to be relatively different, or just different enough, from other systems to dissuade porting the code elsewhere.

[almostdigital]

https://github.com/apple/swift-corelibs-libdispatch

[armadsen]

Yeah. Worth noting too that libdispatch has been open source since it was released 10 years ago. I compiled and used it on Linux before Swift was out.

[mmjaa]

Sure. The solution to not wanting to be dependent on Apple's software is .. to use more of Apples software.

Not really rational.

[iainmerrick]

It’s open source. You can use it on Linux rather than being tied to MacOS or iOS. What’s your objection?

[mmjaa]

Lets try this a different way. Whats so great about GCD that other processor resource management systems get so wrong, that using GCD is the only thing that makes sense to you?

(Hint: its koolaid, kid.)

[iainmerrick]

It’s not a memory management system.