These conversations just don’t make the front page of HN.
On the other hand, it could be that Google owning Go makes the bigger difference. I know that Ian Lance Taylor created several versions of generics that got shot down, which must have been frustrating. However, I don't remember hearing the slightest bit of internal conflict from the core team. (I pick on generics because it was the largest and longest "conflict" in Go's history.)
The primary language developers/owners work at the same company, so presumably they have more bandwidth (behind closed doors) and more financial incentive to provide a united front. Or, they're just a pragmatic group of engineers with drama turned to -11.
1) MS taking control of something the community doesn't want them taking control of
2) Important open source third party library switching to a proprietary license
Rarely do you see drama centered around specific individuals like you see in the Rust or JavaScript communities. So I think that lends some further credence to your theory that the design goals of the language help foster specific cultures around them.
I always felt like he wrote down those non-final designs more as an effort to discover & document why exactly each one wasn't good enough, so they might guide the future design(s). I think he was well aware of the various flaws and unwanted trade-offs, and wanted them to serve as a guide to the conversation.
You're kind of stating this as if nobody in the Rust ecosystem tries that approach first.
The only way to free a project from such entrenched rot is an ultimatum; "You can have the builders or the schemers, but not both".
> I was able to reassure myself, by checking these private discussion places, that there were good people, fighting for the right thing to be done. That things weren’t irremediably broken. That there was hope for improvement in the near future.
I…don't know. What…could he do? What would you tell him?"
To shrug.”