4 ms·
FWIW it hasn't had much uptake within Google. I think the sense that this is a "Google language" is exagerated. What it is is a language created by a certain g
by cmrdporcupine 6y ago
FWIW it hasn't had much uptake within Google.
I think the sense that this is a "Google language" is exagerated. What it is is a language created by a certain group of people at Google with Rob Pike at its origin, and they would have created this language wherever they were working. It's a continuation of the work they did on Limbo/Inferno, etc. not something adapted for Google's needs, as it is sometimes advertised as.
So I'm in no position to criticize Rob Pike, he's a far smarter person than me who has achieved a lot more than I ever will. But I also don't think Go solves any problems that I have, and my one experience with going through Go code review at Google turned me off the language probably forever.
- vl 6y agoWhile hard to say quantifiably, from what I’ve seen almost any new backend service is written in Go (apart from ML-related, which Go doesn’t support). Given that many-many older services were implemented in C++ and Java, these still dominate. Weird quirk of using Go at Google is that any backend service at Big G mostly copies protos, and in Go you end up with these many-page inline protos initializations, which are unreadable.
- vp8989 6y agoCan you elaborate, RE: the Go code review?
- cmrdporcupine 6y agoGoogle has a "readability" restriction for reviewers/authors on CL (changelists, I guess like a pull request). You need a reviewer with readability in a given language to approve your CL before it can land. When I first started, to get readability involved putting together a good archetypal CL in the language, showing good knowledge of the language, lots of tests, good documentation, etc. and then it would go into to a readability queue, get reviewed, and you'd get your readability capability. Go was different in that they had introduced an incremental readability process. Instead of one CL, you had to do many, each reviewed by different people, and over time after doing a whole bunch of CLs you could get readability. This is the process that Google eventually adopted for all languages, but they started with Go. What I found was the Go reviewers were a) exceptionally pedantic [even by Google standards] but, worse, b) very contradictory. One would chastize me for using channels where they were unnecessary, so I'd remove their use and just use simple functions but then a later reviewer would scorn me for not using channels in the same code. It became a painful game of tennis. And the whole thing had a feeling of ideology over practicality.