> If you don't want to use a project affiliated with Google, don't code in Go. For what it's worth (and I say this is an outside observer who's never written a

> If you don't want to use a project affiliated with Google, don't code in Go. For what it's worth (and I say this is an outside observer who's never written any Go, so, grain of salt, etc.), I don't think the original post this responds to disagrees with your point. To wit, from that post: > Or in short, Go has community contributions but it is not a community project. It is Google's project. This is an unarguable thing, whether you consider it to be good or bad, and it has effects that we need to accept. For example, if you want some significant thing to be accepted into Go, working to build consensus in the community is far less important than persuading the Go core team. and > PS: I like Go and have for a fair while now, and I'm basically okay with how the language has been evolving and how the Go core team has managed it. I don't think he's saying "Go is bad" or even "the management of Go is bad," but rather something more like "people should be honest about the nature of the management of Go, and choose how to engage with the community and the process accordingly."