This is old news; it was a semi-troll-ish response to the first trademark policy draft which had people wondering if they can still say “Rust” out loud without summoning a register of lawyers.
More full-troll-ish… anyone who had even the most cursory understanding of trademark law knew the policy was absolutely fine and didn’t substantially alter what they already could (or could not) do with someone else’s trademark.
A semi-troll-ish move would be to fork their fork and call it GreenGlandLang… for those who know that crabs habitually urinate in their own faces.
More full-troll-ish… anyone who had even the most cursory understanding of trademark law knew the policy was absolutely fine and didn’t substantially alter what they already could (or could not) do with someone else’s trademark.
Yeah, this is part of the problem with soliciting the community for feedback. Developers are not at all qualified to read legalese and have no idea how trademarks work.
There were some issues with the policy, but nothing glaring, and nothing nearly as bad as people were implying, like “omg they can sue us for writing rust”.
This doesn’t appear to address any of the concerns brought up recently.
Either crablang is just rebranded source code, in which case it’s beholden to the parent project (trademark aside), or it becomes a full project in its own right, with all the problems of OSS management and leadership that entails.
Maybe they’d do a better job of management maybe they wouldn’t. But nothing here explains how they’d avoid the mistakes made by a certain other volunteer OSS project.
I hope that the controversies around the Rust language leadership subside. The trademark policy was not very well-received. I especially did not like the politicized nature of it. In an ideal world, the Rust project will get it’s act together and that CrabLang will be forgotten. Despire the recent fallout, I regard anyone working on it highly and am hopeful that things will improve.
Yes but the trademark has nothing to do with the project. In contrast the original speaker who resigned was very fond of the rust foundation (which handles the trademark). As opposed to the project which manages the conference.
Hopefully the effective power vacuum since the original mod team resigned will be resolved soon.
This is old news; it was a semi-troll-ish response to the first trademark policy draft which had people wondering if they can still say “Rust” out loud without summoning a register of lawyers.
More full-troll-ish… anyone who had even the most cursory understanding of trademark law knew the policy was absolutely fine and didn’t substantially alter what they already could (or could not) do with someone else’s trademark.
A semi-troll-ish move would be to fork their fork and call it GreenGlandLang… for those who know that crabs habitually urinate in their own faces.
Yeah, this is part of the problem with soliciting the community for feedback. Developers are not at all qualified to read legalese and have no idea how trademarks work.
There were some issues with the policy, but nothing glaring, and nothing nearly as bad as people were implying, like “omg they can sue us for writing rust”.
This doesn’t appear to address any of the concerns brought up recently.
Either crablang is just rebranded source code, in which case it’s beholden to the parent project (trademark aside), or it becomes a full project in its own right, with all the problems of OSS management and leadership that entails.
Maybe they’d do a better job of management maybe they wouldn’t. But nothing here explains how they’d avoid the mistakes made by a certain other volunteer OSS project.
Duplicate of: https://lobste.rs/s/w0dspc/crablang_community_fork_language_named
You’ve just linked to the same thread…?
Haha oh well, the threads have been merged now.
So what makes CrabLang different? Will it grow new features?
Remember the Node fork? Good times. https://github.com/artillery/io.js/
The node fork worked out really well.
Yeah, I think in the long run, it scared people straight.
Finally, a new language. It’s been almost a week!
I hope that the controversies around the Rust language leadership subside. The trademark policy was not very well-received. I especially did not like the politicized nature of it. In an ideal world, the Rust project will get it’s act together and that CrabLang will be forgotten. Despire the recent fallout, I regard anyone working on it highly and am hopeful that things will improve.
Yes but the trademark has nothing to do with the project. In contrast the original speaker who resigned was very fond of the rust foundation (which handles the trademark). As opposed to the project which manages the conference.
Hopefully the effective power vacuum since the original mod team resigned will be resolved soon.
[Comment removed by author]
Why copy the entire text of the linked article? It’s a bit redundant.
I would downvote this if I could, for being super redundant