Just gonna leave a short, and not too in depth reply. OO: Go is great for building server-side software in a fashion where it responds to events. I think it'd

Just gonna leave a short, and not too in depth reply. OO: Go is great for building server-side software in a fashion where it responds to events. I think it'd be interesting to explore a framework built like that, the way ReactiveCocoa sits on top of Cocoa. Type Inference: Like you said, id makes everything dynamic in essence, which loses the value of Objective-C being static type at compile time. GC: My approach tends to be that the compiler/runtime are smarter than me, so I'd rather depend on it than me. Concurrency: Definitely have used libdispatch (all the time...), excluding it is merely an oversight. I was more focusing on channels, and the go keyword is necessary to introduce beforehand for the example. Packages: I believe that if there is no conflict, you can just reference the class name, though I may be thinking of another language. I can see your point for sure though. Thanks for the feedback, would love to hear more of your thoughts on the matter.