Why I Left Rust
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 team's viewpoints or support)Rust members were "uncomfortable" with this purely technical viewpoint - not their behavior, personal beliefs, or even their demographic?And then they pushed them out of the conference behind leadership's back?Did I miss something? This is indeed really childish behavior.EDIT: oh. It's not even reflection, it's compile time reflection. As in, it's not the next Java but instead something that might actually be very useful for the language if done correctly.https://thephd.dev/i-am-no-longer-speaking-at-rustconf-2023> The sudden reversal smacks of shadowy decisions that are non-transparent to normal contributors like myself. It is a brutal introduction to the way the Rust Project actually does business that is not covered by its publicly-available Procedures and Practices and absolutely not at all mentioned in its Code of Conduct.Agreed. The Rust project needs to stamp this out before it begins to fester. This is incredibly stupid behavior coming from what is being regarded as the next C++.Come on, Rust committee. Let's grow up here, shall we?