Re:Understanding the Go Runtime: The Scheduler
by withinboredom on Friday March 13, 2026 @02:27PM
(#47367853)
Heh. I've had my fair share of mailing list drama. This is political AND technical. Someone saying "let’s cut throughput" is going to get shot down fast, no matter the technical merit. If someone with the political clout were to be willing to champion the work and guide the discussion appropriately while someone like me does the work, that's different. That's at least how things like this are done in other communities, unless go is different.
[ Parent
| on HN ]
> If someone with the political clout were to be willing to champion the work and guide the discussion appropriately while someone like me does the work, that's different.
There is unlikely anyone on the Go team with more political clout in this particular area than the one who has already reached out to you. You obviously didn't respond to him publicly, but did he reject your offer in private? Or are you just imaging some kind of hypothetical scenario where they are refusing to talk to you, despite evidence to the contrary?
Re:Understanding the Go Runtime: The Scheduler
by withinboredom on Friday March 13, 2026 @06:02PM
(#47370577)
> You obviously didn't respond to him publicly, but did he reject your offer in private?
I literally have no idea what you're talking about here.
You must not have read all the comments yet? One of Go's key runtime maintainers sent you a message. Now is your opportunity to give him your plan so that he can give you the political support you seek.
Re:Understanding the Go Runtime: The Scheduler
by withinboredom on Friday March 13, 2026 @06:37PM
(#47370920)
I still have no idea what you are talking about.