Did you read the new trademark policy?
Did you read the new trademark policy?
And in section 4.1.3: "You may use the Word Marks, but not the Logos, to truthfully describe the relationship between your software and ours. Our Marks should be used after a verb or preposition that describes the relationship between your software and ours. So you may say, for example, 'the Dungeness tool for the Rust compiler' but may not say 'the Dungeness Rust compiler,' which suggests that Dungeness is the source of the Rust compiler."
It also seems strange that they would allow a different compiler to use the trademark to refer to the language, as in "ABC compiler for Rust", without any requirement that the language implemented by the compiler is in fact the Rust™ language with "the same features and functionality", so that it doesn't create exactly the kind of confusion they're trying to avoid with this policy.
Edit: I'm not necessarily in favor of such conformance requirements. It's a tool that can be used both for good and for evil: Java used it to successfully defend against Microsoft but also to (in effect) prevent Adoptium from distributing OpenJ9.
https://blog.rust-lang.org/inside-rust/2023/04/12/trademark-...
Registered trademarks have to be defended, if you don't defend them they can be invalidated. Forking the language is certainly one kind of feedback. But I get the feeling that most people who have a problem with this new policy would rather that there was no policy at all, no enforcement. I don't think that's very realistic.
a) the trademark getting invalidated
b) creating a chilling effect which robs the community of momentum on meetups, books, tutorials or even just really enthusiastic fan/technical channels like for example https://www.youtube.com/@NoBoilerplate
You don't write a policy like this in such a way that it permits people to use the mark for just anything. It needs to be restrictive, at least a little bit. If it's registered then it needs to be protected; if you allow the indiscriminate use, you lose the trademark (and then just anyone can call their copier a Xerox machine on the package. Now if you're Xerox Corporation you actually do have a problem.)
Then again, I am a Rubyist, so I just went and checked on what trademark policies the Ruby language has, and as it turns out (unless I missed something) there are none. There also isn't a Ruby foundation – there's Ruby Central, the non-profit responsible for organizing the conferences (those are RubyConf and RailsConf) but they don't exert controlling authority over any community outside of the cons. They don't own any trademarks as far as I can tell. Maybe don't need this at all.
There is a Rails Foundation. Another example, not a language but: DHH owns the "Rails" mark and the trademark policy is this extremely reasonable one-pager (that also provides some specific real-world examples of what types of abusive uses it is intended to prevent. It's clear enough to me why we can't have unauthorized "Ruby Rails" dolls for sale by just anyone.)
https://rubyonrails.org/trademarks
I don't know how similar Rust Foundation is to Rails Foundation, but if it is too similar then I think I may begin to understand why people do not like it so much. No offense to DHH.
It does feel kind of circular. "Why is there a trademark policy?" Because we have this trademark and we don't want to lose it. "Why do we have a trademark?" To be held in trust by the foundation. Why do we have a foundation? To protect the interests of the community.
Well, if the community seemingly hates this new policy so much, are we doing that? ---
There is a third option though, you didn't mention: the Rust Foundation could actually listen to the community's feedback and draft a new proposal. I'm sure they won't let their mark get invalidated. I'm less sure they will listen now. (People all seem to have made up their mind that no compromise is possible, from where I sit.)
But maybe Ruby as a counter-example is more helpful than I thought. What company or collective stewards Ruby on behalf of the Ruby community? There isn't one, at least not officially. I used to think of Heroku as the company. Matz, the language's creator was employed there as "Chief Architect of Ruby" – is he still associated with Heroku/SalesForce now?
I don't know. I tried to find out if that is still true, all I found was a Wiki article that says he works somewhere else today. It's unclear if he still retains the title and position at Heroku/SalesForce.
So maybe Ruby didn't need a foundation, or maybe it did. Look at Heroku now. If Ruby was counting on their support, I think we'd all be in some kind of trouble. Maybe we are in trouble. I don't know how you feel about Ruby, but I like it! And I don't feel in trouble, that's good for me, so maybe I see your point.
I hope that we get to have more cool events where practitioners can meet up and advance the state of the art for their favorite language. And I'm frankly not sure if any of this information makes me more or less interested in using Ruby or Rust today. I think I'm fairly indifferent about it all. I don't want to get sued, mainly.
So I guess I do at least understand "Why CrabLang" then.
That's the same as taking homeopathics, "just in case". In the end the only thing that does (apart from possible placebo effect) is signal to everyone that you don't have any understanding of the basics of natural sciences (or in this matter the basics of trademark law).
If you want to flout them and get them to sue you so that you can force it to be challenenged in court and hopefully you win and open the door for everyone else, I'm sure they would all appreciate it.
But even aside from whether it would hold up in court or not, it's already a problem that they even tried to claim such things. They should absolutely be criticized for that.
It is not only impeccably fair to criticize them for that document, but there is no more perfectly fair and unassailable way to do it than by simply taking it at it's word and adhering to what it says.
No matter how you try to slice it, it's just not even slightly unreasonable to simply do what the Rust Foundation commanded everyone to do.