> Just like with the trademark policy fiasco just a month ago
I think those are different. Rust trademark policy is more a case of miscommunication, while this seems more deliberate.
Rust Foundation iirc made a draft statement but rather than saying "We'll take community feedback into consideration" went with a much more vague "We'll might take this into consideration". At least that's my impressions.
It was fairly bad trademark policy forbidding crates from using rust and cargo. `cargo x` 99% of the time was some cargo plugin.
Anyone who's written long contracts know you start with some boilerplate that contains a bunch of stuff and gradually whittle it down till it's just what you need.
The error they made was assuming people would understand that process.
I think those are different. Rust trademark policy is more a case of miscommunication, while this seems more deliberate.
Rust Foundation iirc made a draft statement but rather than saying "We'll take community feedback into consideration" went with a much more vague "We'll might take this into consideration". At least that's my impressions.
It was fairly bad trademark policy forbidding crates from using rust and cargo. `cargo x` 99% of the time was some cargo plugin.