>We haven't really ruled out any of the common stack tech choices. They are all good in their own ways, and have their own tradeoffs - and the intention here was not to spark wars about which tool is the best.This is way diplomatic. Though for me your article has no beef, the Pros and Cons of Go has been repeated here for so many times. I was expecting to see the v.s. stuffs, why this, why that, your thought process and experiments. Right, those are the beefs I wanted from your article but didn't find.
>I think the choice was much more of a proactive choice - we liked Go, we like the way it fitted us - good for fast iterative development upfront, good for the long term, fun to write code in and with a lot of advantages that come with the fact that it's a language designed today - with a lot of lessons learned from the past.
This is not convincing though. As much as I admire Ken Thompson and Rob Pike, I tend to agree with the perspective that Go to C is like Plan9 to Unix. Of course, I could be wrong and am glad to be corrected by insightful comparisons and opinions.