Gregory's Server@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.
|
Top-level
1 comment
|
@jannic Either one person (or multiple people) lied and presented their personal decision as a Rust Project-approved criticism of the talk and the compile-time midterm programming report,
OR
enough of them had misgivings that they could not have the talk or the compile-time midterm programming report, and as a group reached that consensus.
In BOTH cases, they aired that grievance by taking a Rust Project-level decision (through RustConf and not informing me of it themselves) to tell me they don't like the direction. Up until now (literally, as we're talking, as this blog post has gone out!), no Rust Project leadership has explained and/or justified their decision, as either a group or individuals! Using RustConf organizers as a vehicle to initially reveal your disdain for a thing, and not explain that disdain in literally any way after being repeatedly told this is not something we have to do to start with, is extremely sloppy!!
@jannic Either one person (or multiple people) lied and presented their personal decision as a Rust Project-approved criticism of the talk and the compile-time midterm programming report,
OR
enough of them had misgivings that they could not have the talk or the compile-time midterm programming report, and as a group reached that consensus.