4 ms·
> I brought the issue up at my local Go meetup, and no one had ever heard about the rule. They were very skeptical of me. This resonates with my experience wri
by draw_down 6y ago
> I brought the issue up at my local Go meetup, and no one had ever heard about the rule. They were very skeptical of me.
This resonates with my experience writing Golang (plus Bazel) this year. Anything that isn’t working, you must have just messed up and did something wrong. It can’t be that something is actually broken here.
Even in this comment thread, “stop complaining and just do it.”
- throw_m239339 6y agoThis kind of dismissive behaviour have been in the Go community since the beginning, unfortunately. It's the product of Rob Pike's behaviour and his rejection of "complexity". But you can't just dismissing complexity by deeming it irrelevant, it's there. Ian Lance Taylor is probably the only person in the Go team that has a more pragmatic approach to things. The rest is a bunch of deaf people led by the blinds and a few vocal gatekeepers outside Google that will publicly humiliate you if you stray away from the current orthodoxy.
- draw_down 6y ago> But you can't just dismissing complexity by deeming it irrelevant, it's there. This is my sense as well- by refusing to allow complexity in one area, you often just end up forcing it into another area. Moving the toothpaste around the tube. Overall Go was a bad fit for me in ways that come down to differences of opinion, and that's nobody's fault. But I did also come across the dismissiveness you mention. Overall I feel there is a callousness to the community, not just interpersonal interactions but the ways that certain things aren't provided for and tough shit if you don't like it.