6 ms·

But this is the same with any open source project - you can write as much code as you want, but if those with the commit bits decide they don't like it, it's no

• fredsir 7y ago
  > The fact that in Go's case quite a lot of the maintainers work at Google doesn't really change much. It does if those calling the shots aren’t the committers but their bosses. I’m not saying that’s how it is, but if it is, it changes things a great deal.
  • coldtea 7y ago
    It also does since those calling the shots are not just some community members among others that just happened to start the project, but people with job security working on the language, with the money of the biggest sponsor of the language behind them, hosting the infrastructure, doing conferences, and so on. So it's not a level playing field with another contributor.
• coldtea 7y ago
  >But this is the same with any open source project - you can write as much code as you want, but if those with the commit bits decide they don't like it, it's not getting upstreamed. Yes, but seldom those with the commit bits will so blatantly disregard the community as with the case of the community developed dependency solution (and other cases). Especially in projects where those with the commit bits are voted, there would be riots...