2 ms·
I agree the installation issues are fairly trivial; they were just a response to the original comment. But the duplication of effort (which won't end when the
by leereeves 12y ago
I agree the installation issues are fairly trivial; they were just a response to the original comment.
But the duplication of effort (which won't end when the "GoGo" compiler is ready to replace cgo), and a potential freeze in Go while "GoGo" catches up, are more serious drawbacks.
Yes, that is a trade-off other compiler teams have made, and it may be the right choice for Go as well, but it should be (and no doubt has been) considered.