There's an easy fix. Don't comment on stuff when you don't know what you're talking about. It's pretty simple.

If you want a hint on what's wrong, here's one for you: discourse on the Internet sucks in part because of people such as yourself making "clueless" comments.

Thanks for the feedback. Because of the way HN works, it supports a "nonlinear comment development process". You jot some random ideas into a comment, which can often turn into a good comment after several edits (in which those ideas no longer appear at all). Or not: it gets deleted before it is seen: there is a configurable delay before your comment goes public. I was sure that one wasn't going to be (in any shape), but I had to respond to some urgent things. That's it.

> If they aren't coders and are "toxic" on top of that, get rid of them? Looks like a no-brainer to me.

The issue is that, there is no process to do that within the Rust-lang organisation. The core team is only accountable to themselves at this point.

There is no process to get rid of them.

The people who actually make Rust could simply disavow that Core Team.

I suspect there are reasons why it doesn't simply go down like that. Perhaps it's simply a lack of motivaton; or else hands being tied in various ways (invariably connected to money somehow).

Probably the best thing you can do as a FOSS developer is never grab any dollar waved in front of you and put it in your pocket, if you see so much as a tiny, barely discernible cotton fiber connecting that dollar to some people or conditions.

History nerd here: there are processes for when a leadership group no longer serves the public interest and is glued to their chairs.

Defenestration doesn't seem appropriate here.