3 ms·

"We don't have have to go into the details of this" is disingenuous. We can't go into this because he was banned in violation of their own policies for a secon

"We don't have have to go into the details of this" is disingenuous. We can't go into this because he was banned in violation of their own policies for a second time. I agree it likely wasn't related to their DDoS machine, given the past history of bickering between these two parties, but we can't know because Go's own processes were bypassed and someone just arbitrarily lowered the boom. You can carry all the water you want for the Go people, but their handling of this is unprofessional, and it's not the first time they've treated non-Googlers with utter disrespect for no particular gain. This behavior dates back at least as far as issue #9 in their original bug tracker[1], when the most they could muster for their part was the "Unfortunate" bug label, presumably as in "it's unfortunate for you that we're going to do whatever the hell we want." Go's biggest problem isn't generics, or modules, or the infrastructure, or any other technical issue; it's that the creators are the worst sort of ivory-tower academics who have never had to cooprate with anyone outside their friend circle. They get away with it because they ensconce themselves as a club in organizations who can afford to pay people to work in DevRel vacuums, and I'm sure they consider themselves very successful, but Go is easily the most toxically-run language project since the BFDL days of glibc. I have it easy, since I have the autonomy to decide never to get involved with these people, but not everyone has that privilege, and you're not doing the situation any favors by torchbearing for jerks. https://github.com/golang/go/issues/9 https://github.com/golang/go/issues/9

tptacek 4y ago
My reading of this is: "I agree with what you said but I'm still not happy with how they manage things and also they shouldn't call their language Go".
- stonogo 4y ago
  Ok, I guess I can simplify my message: It is not helping anything for you to pretend you know why Drew was banned from the issue tracker, but said ban is consistent with the Go maintainers' shit behavior. I'm sorry I distracted you from the point with all the examples and root-cause analyses.
  - morelisp 4y ago
    > It is not helping anything for you to pretend you know why Drew was banned from the issue tracker This is extremely funny because a) it is true that we don't know why, there are several public and probably more private reasons he could have been banned! take your pick! and yet b) everyone involved agrees it was not due to this ticket, yet discussion of this ticket is always where it gets trotted out.
spencerchubb 4y ago
Who cares that some unknown language was called "Go!" ? If I looked hard enough, I could find an obscure language named Rust that was invented before Mozilla's Rust. Same for Dart, Swift, etc
- zelphirkalt 4y ago
  Hm. As stated like this, it is just an assumption, that you could. I am not convinced. > Who cares that some unknown language was called "Go!"? If we translate this to other areas of life, then this becomes quite problematic. Next time some bigger group of people can name themselves like a smaller group of people and say "Who cares?". Well, the minority cares. But it is indeed a typical move of a tech giant to appropriate names for their own products, with or without intention to create associations in people's heads. On one hand one must draw the line somewhere, where one deems things too insignificant to veto a naming, but on the other hand it is never nice to take another ones name and overshadow it. Aside from that, "Go" really is a silly name, as shown when people write "golang" all the time, to avoid confusion. "Go" is difficult to search for. One would have thought, that a company like Google knows that kinda stuff, but apparently not.

tptacek 4y ago

My reading of this is: "I agree with what you said but I'm still not happy with how they manage things and also they shouldn't call their language Go".

stonogo 4y ago
Ok, I guess I can simplify my message: It is not helping anything for you to pretend you know why Drew was banned from the issue tracker, but said ban is consistent with the Go maintainers' shit behavior. I'm sorry I distracted you from the point with all the examples and root-cause analyses.
- morelisp 4y ago
  > It is not helping anything for you to pretend you know why Drew was banned from the issue tracker This is extremely funny because a) it is true that we don't know why, there are several public and probably more private reasons he could have been banned! take your pick! and yet b) everyone involved agrees it was not due to this ticket, yet discussion of this ticket is always where it gets trotted out.

spencerchubb 4y ago

Who cares that some unknown language was called "Go!" ? If I looked hard enough, I could find an obscure language named Rust that was invented before Mozilla's Rust. Same for Dart, Swift, etc

zelphirkalt 4y ago
Hm. As stated like this, it is just an assumption, that you could. I am not convinced. > Who cares that some unknown language was called "Go!"? If we translate this to other areas of life, then this becomes quite problematic. Next time some bigger group of people can name themselves like a smaller group of people and say "Who cares?". Well, the minority cares. But it is indeed a typical move of a tech giant to appropriate names for their own products, with or without intention to create associations in people's heads. On one hand one must draw the line somewhere, where one deems things too insignificant to veto a naming, but on the other hand it is never nice to take another ones name and overshadow it. Aside from that, "Go" really is a silly name, as shown when people write "golang" all the time, to avoid confusion. "Go" is difficult to search for. One would have thought, that a company like Google knows that kinda stuff, but apparently not.