> you just can’t name your project rust-foo or call your compiler rusty unless it’s actually rustc. Crablang doesn’t change anything about that.
My understanding is the intention is that you can call your project crab-foo or your compiler crabby and be sure that nobody from Crab is going to get upset at you. You had that choice before, too, but now they've come up with a common name for everyone to share.
Sure, but the crab trademark is worthless. And you wouldn't need to fork the compiler to do that. The community, if it wished, could have formally or informally adopted <crab->foo as a naming scheme.
My understanding is the intention is that you can call your project crab-foo or your compiler crabby and be sure that nobody from Crab is going to get upset at you. You had that choice before, too, but now they've come up with a common name for everyone to share.