1) go is not a suitable candidate for android, as most of the api's are object orientated and involve subclassing sdk classes, which would be awkward and painfull on golang, but not so hard on swift.
2) they would pick up a bunch of companies and devs that are currently building high quality apps for iOS, if swift does succeed in abstracting the foundation classes and provide a reasonable abstraction of the UI classes, it would open up the potential of a universal "app" language, for Mac, Linux, android and iOS.
This may be wishful thinking, but it's worth pushing a few Braincells in that direction.
But the ones that kept surviving between OS generations were the ones being sold by the OS / hardware vendors for their systems, not the ones being sold by third party software companies.
You just need to compare the tooling offered for the programming languages that are part of an OS SDK, with the platform support for other programming languages not part of the SDK.
Bringing an external systems programming language means additional development effort, spent in wrapping OS libraries, integration with debugging tools, compiler toolchains.
Hence why many companies are willing only to work with programming languages that have first class support on the platforms they are targeting.
However, there are also some companies for which such issues don't matter. So if there is a big number of such companies, eventually an OS vendor does pay attention and adds such a language into their offerings.
Go I don't like the design, but I will always suggest it to anyone wanting a simple safe C like language.
D, the community is great, but they still need to decide which direction the language is supposed to grow.
Rust community and language are great, but I think they need to get into an OS SDK to really accomplish the goal of replacing C++.
Swift is replacing C and Objective-C as the official systems language on Apple platforms. It has the necessary tooling for full stack applications, IBM is already pushing it on their cloud services and Microsoft will eventually support it on their iOS bridge.
So in what concerns OS vendor support I am betting on Swift.
For the use cases where that isn't relevant, I would say Rust is also a very good candidate.