Re:Go hits the concurrency nail on the head
by lostmsu on Thursday October 04, 2018 @08:58PM
(#18144902)
Well, why did not they just use C#? It already had most, maybe even all of Go's current features.
Hell, the main thing of Go, the go op is basically await.
Re:Go hits the concurrency nail on the head
by JeremyBanks on Thursday October 04, 2018 @09:24PM
(#18145022)
C# would be a good option today, but at the time it was an expensive proprietary closed-source blob maintained by one of their primary competitors, and async/await was still years away. I don't like Go very much, but it was a reasonable choice for Google.
It's interesting, as I don't think Go would have been successful without the pivot, but I also don't think it would have been as successful if they had started off trying to replace Python.