My understanding from afar is that a Rust dev wanted to interact with C code in a way that the C maintainer didn't like. This led to the C dev saying that while he likes Rust, he believes multi-language codebases are cancer and would stonewall all Rust code that touches his code.
Marcan watched it unfold on the mailing list wanted Linus to step in and force the C dev to play nice. Since nothing happened, he went to social media and lashed out as a last resort. That's when Linus finally chimed in and pretty much said "you might be right, but this isn't the way to handle things".
> My understanding from afar is that a Rust dev wanted to interact with C code in a way that the C maintainer didn't like.
He didn't want any Rust code at all touching his turf. He outright NACKed without any technical reason and refused any negotiations with the Rust team that any Rust build fails due to C code breaking changes would be their entire responsibility.
> This led to the C dev saying that while he likes Rust, he believes multi-language codebases are cancer and would stonewall all Rust code that touches his code.
I believe that was an attempt of damage control to save face and he actually meant to call Rust "cancer".
Marcan watched it unfold on the mailing list wanted Linus to step in and force the C dev to play nice. Since nothing happened, he went to social media and lashed out as a last resort. That's when Linus finally chimed in and pretty much said "you might be right, but this isn't the way to handle things".