@jannic RustConf was following the direction and lead of the Rust Project, here. The Rust Project has (still) unaired grievances with the direction of compile-time programming, and chose to air those grievances VIA a talk demotion rather than any actionable or explained feedback (or even just a "We hate this, stop doing this").
That's the core problem. Not RustConf having a hard time; everyone behaved exactly as they wanted to, at no point was the sequence of decisions that led to use here rushed or in-error, or so I've been informed repeatedly.
@thephd Is the "Rust Project" something homogeneous enough to have one opinion about topics like compile-time programming? I don't have internal insights, but I imagine it's a relatively heterogeneous group of people.
Obviously somebody acted in a weird way, intentionally or by mistake. But I have no idea how that could have happened, so I'm not going to point to any particular person or group. I'm sorry if my first message could be interpreted as blaming the RustConf organiziers.