Björkus "No time_t to Die" Dorkus

I don't feel anything these days because I'm a professional. We laid out exactly what would be required for the work would continue, both privately and publicly: for someone to do a technical (or even just a design review) of why they think the work is not good enough, rather than lobbying underhanded attacks this way 'n' that.

Nobody has gotten back to me with those technical details. The work thusly won't continue.

In this same time period, C++ has actually moved its core compile-time reflection mechanisms and work into its Core Working Group, putting it on-track for C++26. Rust had a chance to out-do pretty much all other languages in this space (except D, but D is struggling to be fully relevant) and beat C++ to the punch.

They have, seemingly, declined to do so. But I may not know, because I am not in that community much anymore and only use Rust for private projects. 🤷‍♀️

You know what's fucking crazy? I was trying to ignore all this shit, work directly with the Foundation, and get up to speed for taking the Rust Specification job that I managed to successfully interview for and get an offer from.

But we're going to have to turn it down.

I can only thank @whitequark for speaking up when she did. Otherwise, I'd be Rust Specification editor in the middle of this complete fucking disaster. I'm so sorry this is how it played out; even if I couldn't do code, I genuinely wanted to help make Rust succeed in some fashion.

But it's beyond me now.

Good luck, and God's Speed.

Case in point: dtolnay was also the one thus far unnamed by anyone speaking for the project person who was involved in ThePHD’s talk being downgraded from a keynote.

.... Excuse me?

.... So this is why nobody wanted to mention his name. Why nobody wanted to tell me what the real objections were. This is the Strong Man behind a lot of those kinds of Rust behaviors, huh?

I look forward to a well-written rebuttal for compile-time reflection, then. My blog post included potential examples of automatically-generated, macroless serde code, after all. Maybe that's why he got pissed off enough to try to cut me at my legs. After all,

why address things technically, when you can just dagger somebody in the back under protection from the whole Rust Project who won't say your name?

When someone decides to make up entire bungles of horse shit in their "explanation" and "apology" (https://archive.ph/Utaz1) about the weird shit they did.

I want off this fucking ride.

"Postpone to 2024"? Present at a "tier 2 conference"? My reasoning is contained directly in my blog post (https://thephd.dev/i-am-no-longer-speaking-at-rustconf-2023). If you're going to fucking lie about me at least try and be fucking accurate about it:

It is also deeply confusing and ultimately insulting for them not to contact me beforehand and simply ask me if I would disclaimer my work to make it clear that they did not explicitly endorse this direction. Multiple times before the RustConf schedule and program was released, I made it obscenely clear that there was not going going to be an RFC for the work I was talking about (“Pre-RFC” is the exact wording I used when talking to individuals involved with Rust Project Leadership), that this might bias folks, and whether or not it would be okay to do this. Individuals in contact with me both inside and outside RustConf leadership made it abundantly clearly that this topic was perfectly fine. Furthermore, they had already met to discuss my work before hand, so at no point should anyone be confused about what my intentions and goals are.

That someone would try to use game-of-telephone bullshit to make it seem like I deserved to have my keynote outright removed (which was the ACTUAL SUGGESTION given to RustConf, and they changed it to a DOWNGRADE to prevent bigger fallout from Triplett and Tolnay's CLEAR oversteps and, apparently, outright lies here!), or that I was in agreement with such a removal, when I literally took the required time to make a proper assessment of the situation and respond like an ADULT, is some WILD nonsense!

Is this a common Rust Project occurrence? Do people just do this ALL THE TIME? WHAT IS GOING ON OVER THERE?!

Like. I have pretty bad self-doubt. I pushed through that to accept that talk, and hold my head up high. And then this motherfucker just.... makes shit up. I don't fucking need this, I have my own imposter syndrome to fucking deal with, and this motherfucker just MAKES SHIT UP.

The rest of that statement, modulo that bit, is of course, also bullshit. Trying to conflate Yoshua's struggles as a reason to paint over my work entirely and make it seem like it wasn't ready to present is a personal shortsight of his, and him projecting his inadequacy on me is bonkers. This is the best they could put together after 3 months of this absolute nonsense?

Infuriating that Yoshua catches strays in this statement for the struggle of trying to implement something truly difficult in the Rust ecosystem, but to use it as justification to attempt to bulldoze my work?

The sheer gaslighting in that statement!

But then again, given the background, I can't expect anything less.

Case in point: dtolnay was also the one thus far unnamed by anyone speaking for the project person who was involved in ThePHD’s talk being downgraded from a keynote.

.... Excuse me?

.... So this is why nobody wanted to mention his name. Why nobody wanted to tell me what the real objections were. This is the Strong Man behind a lot of those kinds of Rust behaviors, huh?

I look forward to a well-written rebuttal for compile-time reflection, then. My blog post included potential examples of automatically-generated, macroless serde code, after all. Maybe that's why he got pissed off enough to try to cut me at my legs. After all,

why address things technically, when you can just dagger somebody in the back under protection from the whole Rust Project who won't say your name?

When someone decides to make up entire bungles of horse shit in their "explanation" and "apology" (https://archive.ph/Utaz1) about the weird shit they did.

I want off this fucking ride.

"Postpone to 2024"? Present at a "tier 2 conference"? My reasoning is contained directly in my blog post (https://thephd.dev/i-am-no-longer-speaking-at-rustconf-2023). If you're going to fucking lie about me at least try and be fucking accurate about it:

It is also deeply confusing and ultimately insulting for them not to contact me beforehand and simply ask me if I would disclaimer my work to make it clear that they did not explicitly endorse this direction. Multiple times before the RustConf schedule and program was released, I made it obscenely clear that there was not going going to be an RFC for the work I was talking about (“Pre-RFC” is the exact wording I used when talking to individuals involved with Rust Project Leadership), that this might bias folks, and whether or not it would be okay to do this. Individuals in contact with me both inside and outside RustConf leadership made it abundantly clearly that this topic was perfectly fine. Furthermore, they had already met to discuss my work before hand, so at no point should anyone be confused about what my intentions and goals are.

That someone would try to use game-of-telephone bullshit to make it seem like I deserved to have my keynote outright removed (which was the ACTUAL SUGGESTION given to RustConf, and they changed it to a DOWNGRADE to prevent bigger fallout from Triplett and Tolnay's CLEAR oversteps and, apparently, outright lies here!), or that I was in agreement with such a removal, when I literally took the required time to make a proper assessment of the situation and respond like an ADULT, is some WILD nonsense!

Is this a common Rust Project occurrence? Do people just do this ALL THE TIME? WHAT IS GOING ON OVER THERE?!

Like. I have pretty bad self-doubt. I pushed through that to accept that talk, and hold my head up high. And then this motherfucker just.... makes shit up. I don't fucking need this, I have my own imposter syndrome to fucking deal with, and this motherfucker just MAKES SHIT UP.