this post was submitted on 04 Sep 2023
30 points (100.0% liked)
Rust
5999 readers
4 users here now
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Wormhole
Credits
- The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Is there really a "fiasco" because somebody can't hold a talk? Am I getting this right?
No, not really.
Months ago, there was a fiasco because somebody's keynote talk was suddenly and inexplicably downgraded to a regular talk because the Rust Project "did not want to endorse" the talk, despite nominating and encouraging the speaker in the first place. This resulted in the speaker withdrawing their talk, and multiple public apologies from some of the people involved. https://thephd.dev/i-am-no-longer-speaking-at-rustconf-2023
https://hackmd.io/@Manishearth/SkLZzzbLn
https://gist.github.com/m-ou-se/ca7d7edf778a9b93b812512b3d8288f5
Currently there is a fiasco because it turns out (one of?) the voices behind the inexplicable decision to downgrade the talk was dtolnay, lead Serde developer, who recently came under fire for publishing precompiled proc macro binaries in Serde and his response to the ensuing criticism. The perception is that dtolnay, who has done lots of work with proc macros and made several detailed suggestions as to their future in Rust, quashed the RustConf talk because he disagreed with the premise of the talk in favor of his own ideas about macros.
Thank you for the context. That was a good summary.
I think people consider it a fiasco because of the amount of backlash, drama, and accusations that surrounded it. The whole thing showed failures in the way things were decided and communicated as well.