3 ms·
> Besides Vitess, what other high profile usage is there at Google? The piece of software that runs on dl.google.com, which serves millions of Chrome updates e
by _ak 14y ago
> Besides Vitess, what other high profile usage is there at Google?
The piece of software that runs on dl.google.com, which serves millions of Chrome updates every day, is written in Go. The problem is: you're asking for Go success stories at Google, even though most of Google's internals will never be published. Why don't you just take a closer look at other companies' success stories and acknowledge them?
> Not to mention they offloaded part of the implementation to Memcache because Go wasn't good enough.
Huh, what? Using memcached means the technology you use isn't good enough, or what are you trying to suggest? Don't forget that the author of memcached is a core Go developer at Google, so I'd say they know what they're doing.
- bobbydavid 14y agoCan anyone explain why this was downvoted?
- _ak 14y agoBecause HN jumped the shark and is now basically Reddit in a different color theme.
- codexon 14y agoI didn't downvote it, but it was downvoted for a good reason. He didn't spend much effort to understand a simple sentence. http://code.google.com/p/vitess/wiki/ProjectGoals#Why_did_we_choose_go http://code.google.com/p/vitess/wiki/ProjectGoals#Why_did_we... > Go’s existing mark-and-sweep garbage collector is sub-optimal for systems that use large amounts of static memory (like caches). In the case of vtocc, this would be the row cache. To alleviate this, we intend to use memcache for the time being. For a self-described systems level language this is ridiculous. I would like Go to replace C++ and Java, but false optimism won't make this happen.