Sourcehut will not blacklist the Go module mirror
sourcehut.org
sourcehut.org
Sourcehut will blacklist the Go module mirror - https://news.ycombinator.com/item?id=34310674 - Jan 2023 (337 comments)
I'm also still questioning the need for the proxy in the first place.
The main problem is none of this was communicated very well.
You really think the team worked for two years on a solution while banning the issue reporter and keeping radio silence, and then by pure coincidence got it ready shortly after a complete block of their service was announced?
We don't have to go into the details of this if DeVault doesn't want to; it's enough to say that the narrative that Google blocked him to shut him up about the Go Module Proxy seems implausible at this point. I don't see him saying that in the first place! But people here are.
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.
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.
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.
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
> 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.
Again, arguably this took too long. They certainly didn't communicate well. But that they were already working on it before the block announcement can be easily demonstrated.
/me remembers years of being gaslit by Gophers, of all stripes, for asserting that, no, unlike the cult of personality around Go, i did actually know what i was talking about when I said GOPATH was a nightmare in real world use (even better, it was plainly obvious even with pre-1.0 kubernetes). Just cringey.
For all the handwavey whinging about Rust, Gophers have treated me far more poorly over things that have been retconned and forgotten years later.
I personally find people saying something is a garbage dump, nightmare and fire whatever Rather than explain the issue to be credibility reducing phrases
Don’t recall what gopath was sold as a fix for
Feel free to google the word, then the behavior I described, then look at the peer comment where someone literally goes "idk what that long-since killed-off-thing was but you must be exaggerating".
Thanks for ironically proving my point and demonstrating just how ignorant the criticism was.
I can't get my head around this. I describe a feature, that has long since been ret-conned from the community because it became such a thorn in everyone's side.
And you're just like "nah it probably wasn't that bad even though it was excised and is no longer talked about *and I can't even remember what it was for*" (despite being the exclusive only way to do local dep management). Stun-ning.
What is was "sold as a fix for"? Man, the hubris of people commenting on things literally completely ignorantly.
LOL, really didn't think I'd be gaslit about GOPATH in 2023. Brilliant, keep it up Gophers!
Everyone hates, nightmares, dumpster fire, brain dead, useless, everyone knows, ignorant.Are examples.
Say someone writes “Working on Mac/Linux/windows is a nightmare”, ok … what does that convey ?
Only because DeVault complained do we see that things were happening. Information, but still no control.
It's only when DeVault started to actually annoy Google with real visibility that they decided to take responsibility for what they were doing.
There's an interesting analogy to class struggle, where DeVault uses his leveraging power of striking to make the big Kapitalist change their ways and assume responsibility of asking too much to the little hands doing the actual work of hosting.
I am stunned it took so much kerfuffle to get there. Why is it not the default behavior ?