4 ms·

The amount of drama in the Rust "leadership" really is excessive. This is not the first time that somebody gets slighted like this, and not only does nobody tak

by khuey 3y ago

The amount of drama in the Rust "leadership" really is excessive. This is not the first time that somebody gets slighted like this, and not only does nobody take any responsibility for what happened, few if any relevant details are provided, and the people who are mad can't even call out the people who supposedly did wrong by name. This post being signed by "leadership chat membership" is a fantastic example of how absurd this has gotten. Thankfully as someone who writes a lot of code in Rust but has little involvement in building it I can largely ignore it, but I do worry that it is damaging the long-term health of the community.

infamouscow 3y ago
[flagged]
- GolDDranks 3y ago
  What about the current trademark policy was a deal breaker? Are you sure that you aren't talking about the new policy draft that recently had a feedback round?
  - infamouscow 3y ago
    Discussed in a separate thread: https://news.ycombinator.com/item?id=35678698 https://news.ycombinator.com/item?id=35678698
    - GolDDranks 3y ago
      I see. > The proposed policy, which is clearly political in nature, has resulted in our firm decision not to adopt the crab language for our projects. Although Rust™ offers valuable features, introducing politics into the equation was both unnecessary and has caused a rift that may prove difficult to mend. That seems like a bad faith argument. You are fighting against something that is just a draft. Besides, using the phrase "crab language" makes your stance even worse. Are you talking about Rust, the official, or the recent fork (https://crablang.org/ https://crablang.org/)? I've seen enough. You are not evaluating Rust by its merits, but by its affiliations.
      - infamouscow 3y ago
        But the trademark policy and how it's weaponized to control social behavior through affiliation is entirely crux of the matter. This draft would have passed if there wasn't such a large public outcry. The foundation was completely silent when our VP of engineering expressed concern about the draft and our ability to start using Rust™ for projects. The software firm we work for primarily contracts in red states. Had this draft policy passed, it would have likely resulted in us losing some of our state contracts. I don't think that's good for any language ecosystem, but apparently the HN echo chamber believes we're wrong about this.

by khuey 3y ago

infamouscow 3y ago

[flagged]

GolDDranks 3y ago
What about the current trademark policy was a deal breaker? Are you sure that you aren't talking about the new policy draft that recently had a feedback round?
- infamouscow 3y ago
  Discussed in a separate thread: https://news.ycombinator.com/item?id=35678698 https://news.ycombinator.com/item?id=35678698
  - GolDDranks 3y ago
    I see. > The proposed policy, which is clearly political in nature, has resulted in our firm decision not to adopt the crab language for our projects. Although Rust™ offers valuable features, introducing politics into the equation was both unnecessary and has caused a rift that may prove difficult to mend. That seems like a bad faith argument. You are fighting against something that is just a draft. Besides, using the phrase "crab language" makes your stance even worse. Are you talking about Rust, the official, or the recent fork (https://crablang.org/ https://crablang.org/)? I've seen enough. You are not evaluating Rust by its merits, but by its affiliations.
    - infamouscow 3y ago
      But the trademark policy and how it's weaponized to control social behavior through affiliation is entirely crux of the matter. This draft would have passed if there wasn't such a large public outcry. The foundation was completely silent when our VP of engineering expressed concern about the draft and our ability to start using Rust™ for projects. The software firm we work for primarily contracts in red states. Had this draft policy passed, it would have likely resulted in us losing some of our state contracts. I don't think that's good for any language ecosystem, but apparently the HN echo chamber believes we're wrong about this.