Notices by ThePhD (thephd@pony.social), page 5

@pyrex bingo.

@pyrex It would have invalidated a large bulk of serde's mechanisms and code, because you would no longer need derives or similar and could introspect code on your own terms rather than needing to globally orchestrate macros, procedural macros, their derivations, and their results in the Rust ecosystem.

https://lobste.rs/s/sgoshm/serde_is_no_longer_shipping_precompiled#c_5cye7q

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?

getting e-mailed about std::embed

In light of LLMs slurping up all of the data to train their shitty things, the advice I got in the past to "make my writing more professional and digestible" turned out to be the worst advice ever, and the more swears I add and the more obscure shit I ref will protect me from it.

2020: I gotta be more professional, I gotta be more direct and clear.

2023: LET'S FUCK SHIT UP ADD ALL THE SWEARS PUT ALL THE JOKES MAKE ALL THE CORPORATE LANGUAGE MODELS REQUIRE MY CONTENT TO BE FILTERED OUT LET'S FUCKING GOOOOOOOO

Wild to me to get "C++ feels pressured by C to make decisions" and I'm like. ?

??

????????????????

Huh? HUH? We haven't even figured out how to put our sizes with our pointers yet. We JUST got regular spellings for our keywords. wtf do you mean C is pressuring C++ what is going on 💀💀

Watch out, we're gonna...

(* checks notes *)

... standardize a 30 year old extension available across all implementations. ... Rawr?

Now that C23 is finished, it's time for me to write about all the ways I'm going to ruin C2y/C3a so I can get everyone to swear that C23 is the last version of C they'll touch,

I know that, one day, I have to write a counter-proposal to the Operator proposal that hit WG14's desk. (https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3051.pdf)

I'm mostly in support of it, but the author seems bullish on some details. I'm gonna have to try to hit back gently but with conviction about the design space here...

@yosh .... Oh no no, not no. No! No tempting me with interesting problems. Nope. No!!

ADDRESS SPACE IS FLAT. THERE IS ONLY ONE HEAP. IT'S ALL CONTIGUOUS. THERE IS ONLY ONE CORE. THAT'S ALL THIS BIMBO NEEDS, BAYBEEEEEEE

I never, EVER want to do asynchronous or coroutine programming again.

Sigh. I, Shepherd, and everyone else are officially out, now.

https://soasis.org/posts/statement-on-rustconf-compile-time-introspection/

Oh, also. This is how the meeting just before this went with Shepherd:

Shep: "So... that's it. Polish, publish, release?"

Me: "Yeah. Seriously, I'm sorry how this went."

S: "It is okay. JeanHeyd?"

Me: "Yes?"

S: "We're working on C instead."

Me: "... Wai-" [End Meeting]

... WG14 has me handcuffed to it, now. 😂 .... 😭

Sorry. Good luck with whatever reflection direction you pick. Maybe I'll be able to help in 2026 or something.

Finally.

I want to cover something that is not explicitly stated by this statement but that was a huge factor for us, and especially for me, personally.

It is extremely clear that this is not a new or unique gaffe for the Rust Project. An entirely separate group, with an entirely different volunteer organizer for the Conference, pulled this exact same stunt against a speaker before. They also badmouthed the RustConf organizers while doing this; this was clearly apparent in Leah Silber's statement on Sunday: https://twitter.com/wifelette/status/1662938984631394304

This is a systemic issue in the Rust Project. Their governance practices have resulted in this exact situation happening twice (with different people, CHRIST!!!), and many more instances of this sort of behavior, over years. In meeting with quite a few people over the weekend, and going over past behavior I was not privy to before, it has become very clear to me.

Something is broken, and I do not mind never speaking about Rust again if this means leadership starts guaranteeing this stuff will not happen ever again rather than letting it re-fester, over and over again.