Why I Left Rust
Wait. Let me get this straight.<p>Someone is an expert in this field.<p>They&#x27;re asked to speak at RustConf after a leadership vote.<p>They&#x27;ve also written an article about reflection in Rust - a purely technical thing that is already pretty widely disliked conceptually. (EDIT: the talk <i>was</i> about this, but it&#x27;s also compile time reflection and came with the usual disclaimer that it was not representative of any of the Rust team&#x27;s viewpoints or support)<p>Rust members were &quot;uncomfortable&quot; with this purely technical viewpoint - not their behavior, personal beliefs, or even their demographic?<p>And then they pushed them out of the conference behind leadership&#x27;s back?<p>Did I miss something? This is indeed really childish behavior.<p>EDIT: oh. It&#x27;s not even reflection, it&#x27;s compile time reflection. As in, it&#x27;s not the next Java but instead something that might actually be very useful for the language if done correctly.<p><a href="https:&#x2F;&#x2F;thephd.dev&#x2F;i-am-no-longer-speaking-at-rustconf-2023" rel="nofollow">https:&#x2F;&#x2F;thephd.dev&#x2F;i-am-no-longer-speaking-at-rustconf-2023</a><p>&gt; 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.<p>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++.<p>Come on, Rust committee. Let&#x27;s grow up here, shall we?