"Most of the server's activity is spent on waiting for IO and managing concurrent socket based connections." That sounds like a story I've heard a hundred time

"Most of the server's activity is spent on waiting for IO and managing concurrent socket based connections." That sounds like a story I've heard a hundred times before. For the cases where it's true, good engineers have already been using one of the many other languages that fills that niche. For cases where that's not the primary problem, Go doesn't help. That doesn't mean Go isn't a better option for some use cases. Great. I just don't understand why it's worth reinventing the universe to get something a little better for some use cases. Fine with me -- I'm not the one doing the work. I am just saying that I don't get it. Especially for Google, a company which could have really made a difference in the way we write software.