4 ms·

I can't really speak for Drew's problem with the workaround, only my own from a design point of view - he may not even agree with my own issue at all for all I

I can't really speak for Drew's problem with the workaround, only my own from a design point of view - he may not even agree with my own issue at all for all I know, so I don't want to put words in his mouth. From my own perspective, however, the issue is about impact and responsibility. The excess traffic is their impact as it is caused by their design and is entirely of their choosing. Thus it becomes their responsibility. The workaround they offer (as with so much in tech) means their stuff becomes opt-out and not opt-in. By which I mean their own decisions/designs cause an impact where they require everyone else suffering from it to specifically and individually opt-out of being excessively polled. This is an outrageous requirement they can only impose due to the power imbalance.

tptacek 4y ago
It sounds like DeVault let them know their proxy was hitting his service too hard, and they immediately responded by saying they could dial it down. Seems like a pretty normal sequence of events? I feel like I have to be missing something here.
- jum1p 4y ago
  I can't speak for Devault, either, but I think that Sourcehut is intended to be selfhosted if you want. So it's probably too much pain to ask every language provider (might be a lot) to dial down the traffic. Imagine youre hosting modules from ~200 langs.
- philosopher1234 4y ago
  This is probably 80% peoples' existing animosity towards Google & Go, so they're ready to hate, regardless of how the facts land. I think its primarily about the Go team having a different working philosophy than the standard HN soft. dev philosophy, and an intolerance of difference.
  - kcartlidge 4y ago
    > This is probably 80% peoples' existing animosity towards Google & Go, so they're ready to hate, regardless of how the facts land. Go is my second fave after C# and I've used it almost daily for many years. No animosity here.
- kcartlidge 4y ago
  > It sounds like DeVault let them know their proxy was hitting his service too hard, and they immediately responded by saying they could dial it down I'm not ignoring that Drew complained and they offered to dial it down. That's a reasonable response if it were an isolated case. The problem is that it isn't an isolated case. This is how the module cache works, which means it is doing that kind of load against other module sources too. If you're going to impose these resource demands on others then they should be managed for everyone affected not just the one who complains about it. - Repeatedly pulling an entire repo over and over again is an antisocial act that is unfairly imposing bandwidth/CPU costs on third parties - They should not expect every impacted party to obtain an opt-out individually because of unasked-for extra resource demands - The system that excessively polls is broken, not its victims

tptacek 4y ago

It sounds like DeVault let them know their proxy was hitting his service too hard, and they immediately responded by saying they could dial it down. Seems like a pretty normal sequence of events? I feel like I have to be missing something here.

jum1p 4y ago
I can't speak for Devault, either, but I think that Sourcehut is intended to be selfhosted if you want. So it's probably too much pain to ask every language provider (might be a lot) to dial down the traffic. Imagine youre hosting modules from ~200 langs.
philosopher1234 4y ago
This is probably 80% peoples' existing animosity towards Google & Go, so they're ready to hate, regardless of how the facts land. I think its primarily about the Go team having a different working philosophy than the standard HN soft. dev philosophy, and an intolerance of difference.
- kcartlidge 4y ago
  > This is probably 80% peoples' existing animosity towards Google & Go, so they're ready to hate, regardless of how the facts land. Go is my second fave after C# and I've used it almost daily for many years. No animosity here.
kcartlidge 4y ago
> It sounds like DeVault let them know their proxy was hitting his service too hard, and they immediately responded by saying they could dial it down I'm not ignoring that Drew complained and they offered to dial it down. That's a reasonable response if it were an isolated case. The problem is that it isn't an isolated case. This is how the module cache works, which means it is doing that kind of load against other module sources too. If you're going to impose these resource demands on others then they should be managed for everyone affected not just the one who complains about it. - Repeatedly pulling an entire repo over and over again is an antisocial act that is unfairly imposing bandwidth/CPU costs on third parties - They should not expect every impacted party to obtain an opt-out individually because of unasked-for extra resource demands - The system that excessively polls is broken, not its victims