3 ms·
About 30 mins into the presentation, Rob Pike does give a few examples of real Go usage inside Google. In the end he even mentions a few products that use it, l
by DanielRibeiro 14y ago
About 30 mins into the presentation, Rob Pike does give a few examples of real Go usage inside Google. In the end he even mentions a few products that use it, like Youtube and dl.google.com
- Maxious 14y agoNot to mention Google Public DNS http://wilmer.gaa.st/blog/archives/58-Google-Public-DNS.html#c165 http://wilmer.gaa.st/blog/archives/58-Google-Public-DNS.html...
- rossj 14y ago"While BIND (written in C) can only serve 1000 queries per second on an old 486, the Go rewrite can serve all DNS queries in the world" Maybe I mis-read it, but that comment comes across as a little sarcastic. Hope I'm wrong.
- Evbn 14y agoIf I were charitable, I would say that the Go version supports horozontal scaling and external caching and queue buffers in a way that the BIND does not.
- coldtea 14y agoThose have been the 2 major products that use it for like 2 years. One is a database load balancer (in YT), not the most essential or irreplaceable piece of infrastructure (ie. they can write it in another language whenever they want if the need arises without messing other stuff) and the other is a services that was not updated anymore, and was left to die, before someone from the Go team asked and re-wrote it in Go. It's not even the full download service, just a part of it IIRC.
- Evbn 14y agoTo be clear: a broken product that was actively annoying users and that no one knew how or had energy to fix, got fixed by a Go dev, and you are saying that is NOT a point in Go's favor? Maybe if Reader were written in Go, it wouldn't have been killed.
- coldtea 14y ago>To be clear: a broken product that was actively annoying users and that no one knew how or had energy to fix, got fixed by a Go dev, and you are saying that is NOT a point in Go's favor? Sure is a point in Go's favor. It means it can be used to solve an actual problem in a large company. But what I'm saying is it's not that big of a deal as it may seem to some: it's not like they used Go in some highly critical for them infrastructure or important new project. On the contrary: they used it at so low a priority project, that it was abandoned and left to rot before somebody volunteered (was not even asked!) to do the rewrite. (And, no, it was not abandoned because it's C++ codebase meant it could not be fixed -- after all it could be redone from scratch in C++ or Java, as it was redone from scratch in Go. It was merely due to neglect). So, my point it, this story is not a "investing internally in the language big time" thing, but rather baby steps.
- Evbn 14y agoYou say the big company is not investing in a big way, I see a small team of revolutionaries rescuing a behemoth from crushing itself under its own weight. :-)