3 ms·
> Do you work at Google? I did for over 5 years. While I left before the Go programming language was released, I seriously doubt they've transitioned much of t
by weareconvo 14y ago
> Do you work at Google?
I did for over 5 years. While I left before the Go programming language was released, I seriously doubt they've transitioned much of the codebase to it, for one simple reason:
The Google codebase is fucking massive. I simply cannot describe how unbelievably huge it is, and while I don't doubt for a second that Go will be used for some of the systems-level projects (some of which Rob Pike is directly involved with - how's that for vague), you simply don't transition that big of a codebase to a new language.
It would basically be impossible... unless you're Jeff Dean.
- justin66 14y agoThank you. That's fair, but I think a better metric of the success of Go - which is how this train of thought started - would be how much new stuff is being started with it, for just the reason you stated. It'd be nutty to rewrite a bunch of working code.
- weareconvo 14y agoIn addition to the difficulty of rewriting existing code, even when you program something new at Google, you'd be a fool not to leverage what infrastructure already exists. If you try to do that while at the same time writing the new project in Go, you run into weird interoperability issues.
- Evbn 14y agoDo you know whether Go is compatible with Google infrastructure? With protobufs and stuff like SwIG/JNI, why would it not be?
- weareconvo 14y agoThat's a good point, though protocol buffers aren't used for everything. There's more tightly-bound systems stuff going on, plus libraries and so forth. Which is to say, I have no idea.