3 ms·

While in general, I agree with that quote, I don't think that we have a problem with the Go core team in that respect. I think they do understand the problem bu

While in general, I agree with that quote, I don't think that we have a problem with the Go core team in that respect. I think they do understand the problem but don't really have a solution. I mean, the community has (so far) just a few cases were decisions of the core team were 'not so good'. Sometimes because we didn't like the process and sometimes because of the outcome. But I guess, in general, the majority of Go users likes what the core team does. The problem is more about that many of us have a problem with Google (for a myriad of reasons) and seeing that the core team is tied so deeply into that company makes us worry about future decisions of the core team (as you said). But what could/should the core team do about it? Suggestions?

phillipcarter 7y ago
This is partly why, from the perspective of another person at a company working on a language used by people, it's important to: 1. Embed yourself in the community rather than shy away from it. It's impossible to escape the criticism of "acting on behalf of the company", but being a member of the community can certainly help perception problems 2. Act more slowly on accepting things so that as many voices as possible can have a say 3. Scope what you do to what you're capable of doing _well_ Even if a given feature for a given release isn't what the majority want, people will use it if it solves a problem and is designed and implemented thoroughly.