Hacker News Reader

Comment by morelisp | Hacker News Reader

I did read it. I also read Go 1.19's release notes when they came out. I also read rsc's reply to the original post. I cannot figure out how Drew went back in time to add -reuse to Go 1.19 and proxy improvements to the Go team's schedule prior to the Go team contacting him in private.

View on HN

I think the context you're missing is that Drew caused a stink about this already back in 2021, the blacklisting was just the last iteration of the saga. So I'm not sure if his posting caused the Google team to rethink their stance, but it certainly caused quite a bit of bad publicity for Google.

> Drew went back in time to add -reuse to Go 1.19 and proxy improvements to the Go team's schedule

where did anyone say that?

You did, when you wrote the words "Because of his actions", is I think what they're saying.

Yes. As far as I can tell, the only relevant action sr.ht did was to open #44577 originally. Everything else since then appears to be sound and fury.

well, he could have done nothing, and where would we be? if you say "exactly where we are now", I think you are being dishonest with how the situation played out.

No, he didn't write the code or make the schedule, but he stood up and said "this is not right", and took steps to protect his and other small sites.

To be clearer: I think what's being said upthread is: Go was making this change anyways.

(I have no idea if that's true.)

Reply on news.ycombinator.com