Today, I once again wake up worrying about #Rust 's future.

Why is a shitbag such as #dtolnay still allowed to single-handedly maintain fundamental libraries for the ecosystem? Why is he part of Library API team? How is he not permabanned for single-handedly permanently damaging Rust by killing off comptime reflection over his racism? How is he not permabanned for the power play he attempted to pull with his "RFC" after pushing pre-compiled binary to serde without notice? Why are MIC companies routinely tolerated at Rust conventions? Why does no one talk about it, despite the problems not being solved? Has #Ruby takeover taught people nothing? Will Rust survive another year without turning into #fashtech?

So many questions. I think about them every time I use Rust, which is often.

Apropos of nothing.

#RustLang #serde #FOSS #OSS #OpenSource

@KFears wait dtolnay is racist? where can i read more about that?

also why the hell lately all the tech is becoming fascist, as a trans jewish individual this shit is worrying as fuck

@vavakado @KFears this is referring to a situation a couple years ago where a chain of actions from several well intentioned people caused a keynote for RustConf to be canceled which was kicked off by dtolnay which people quickly assumed was driven by racism before the facts were known which was compounded by at least one well known Rust community member (but outside the project) making a racist comment that the speaker was only chosen for diversity (they were not). The weight of blame put on dtolnay was made worse by them taking limited responsibility for their part including delaying an apology until they were outed and then doing a poor one.

It also has not killed off comptime reflection, just that approach from that contributor. There is on going work in that area by a compiler team member that I am much more hopeful about the design of.

This isn't that I'm a dtolnay apologist. Its just that to work to solve problems you need to make sure you know what the problems are.

@epage @vavakado @KFears i haven't ever heard an apology and you haven't linked to one, or indeed to anything at all despite assuming the authoritative tone of knowing what the problems are we need to solve. i think tolnay can speak for himself rather than having the entire leadership continuing to cover for him and attempting to memory hole the incident.
@epage @vavakado @KFears the only response i've seen from tolnay was not an apology and was a deleted github gist. i've contributed to his crates before in order to allow libsignal to depend on him. i am now taking whatever means are necessary to avoid introducing a dependency on a racist into my dependency graph, since they believe absurdities and are therefore quite dangerous in a supply chain.
@epage @vavakado @KFears perhaps steve klabnik would prefer to go on the oxide podcast again to describe tolnay's most objectionable episode as the time he worked around cargo's lack of a precompiled binary distribution mechanism, caching system straight from the 1900s, and complete failure to represent generalized build products generated by scripts in an auditable and overridable way by precompiling a macro in serde on x86. i believe the term "untrustworthy" was used to describe tolnay—not for fucking up rust's image indefinitely in a very public way, but for veering even slightly outside the chain of command.
@epage @vavakado @KFears one additional benefit of the rustc build system i'm working to prototype right now which replaces cargo and bootstrap entirely is that it also loses the 9000 transitive deps on the david tolnay cinematic universe. this would avoid blocking on the long tail of gccrs compat while overcoming the two main reasons potential new rust users outside the weapons and surveillance industry (radical queers much like the ones who built rust into what it is now) can't allow themselves to invest long-term into rust as a platform for new heights of safety and empathy.
@epage @vavakado @KFears this statement was worse than saying nothing. please understand that we are now facing the prospect of a stallman-like figure who risks losing an entire generation of talent from rust. please try harder. i need you to try harder because i've invested so much into this language with so little to show at the end