4 ms·
Compare that to virtually zero notable stories of C++ projects switching to Go. A lot of projects at Google have switched from C++ to Go, and the people I
by cbr 11y ago
Compare that to virtually zero notable stories of
C++ projects switching to Go.
A lot of projects at Google have switched from C++ to Go, and the people I know who work on them are pretty excited about working in Go. Here's a blog post by a coworker who leads the Chrome Data Compression Proxy project:
http://matt-welsh.blogspot.co.uk/2013/08/rewriting-large-production-system-in-go.html http://matt-welsh.blogspot.co.uk/2013/08/rewriting-large-pro...
- jasode 11y agoThanks for the example. I think your coworkers' rewrite further reinforces the "sweet spot" for Go. The transcoding was left as C++ but the other stuff including the networking was rewritten in Go. That makes sense to me because transcoding is performance intensive and cpu-bound instead of io-bound. (E.g. CPUs pegged at 100% while bytes being read at a slow 10MB/sec.) In other words, if people tried to rewrite ffmpeg in Golang, a conversion job such as avi to mp4 would run slower. If Google's internal cpu-bound projects switched from C++ to Golang, that would be a very interesting data point. In other words, I don't expect Google would switch their machine-learning algorithms scanning petabytes of data from C++ to Go (or create greenfield machine learning projects using Go instead of C++).
- akerro 11y agoWell... you know, G+ is full of Google Employees...