Wait. Let me get this straight. Someone is an expert in this field. They're asked to speak at RustConf after a leadership vote. They've also written an article about reflection in Rust - a purely technical thing that is already pretty widely disliked conceptually. (EDIT: the talk was about this, but it's also compile time reflection and came with the usual disclaimer that it was not representative of any of the Rust…
> They've also written an article about reflection in Rust - a purely technical thing that is already pretty widely disliked conceptually. Maybe that really is the problem. Too much reflection leads to clever, but hard to debug hacks. Look what happened with C++ templates and, further back, LISP macros. That way lies code that's unusually hard to read and maintain. Rust probably shouldn't go that way. Do you want to…
That's what I think most people find terrible about Rust leadership's handling of the situation. It's not that this specific keynote was super important, it's that the team let the speaker spend a few weeks preparing a keynote and then pulled the rug on him.
[0] https://thephd.dev/i-am-no-longer-speaking-at-rustconf-2023