[jamieomatthews]

> With Google Go, there was no real incentive to use it

I don't like the comparisons to Go in this article. I'm an iOS developer who has dabbled in Go, and I'd actually argue the opposite.

For me, there is little reason to immediately switch to Swift. I can still use ObjC, and in fact, I'd expect problems when switching to Swift.

Go, however, had many incentives to learn. Easier deployment, speed, concurrency, etc.

As usual, Wired has over simplified the argument