4 ms·

TLDR: "We use Rust. We will do stuff. It'll be great!" No offense to Niko, but this is a completely vacuous post without a single concrete promise. I don't re

TLDR: "We use Rust. We will do stuff. It'll be great!" No offense to Niko, but this is a completely vacuous post without a single concrete promise. I don't really see the point, except for PR, recruiting or internal signaling.

kbenson 6y ago
> No offense to Niko, but this is a completely vacuous post without a single concrete promise. Why does it need a promise? > I don't really see the point, except for PR, recruiting or internal signaling. It's messaging, sure. What's wrong with that? To me it looks like exactly what it says it is, communication regarding how they want to purport themselves in the community and what they're aiming for.
- the_duke 6y ago
  > communication regarding how they want to purport themselves in the community But the post is titled "How our AWS Rust team will contribute to Rust’s future successes", but doesn't actually say anything - at all. It's all just empty words without content. Apparently the mods agree, since the submission was downranked and blocked from the front page. Or maybe the algorithm picked up the odd upvote count and critical comment downvoting that is quite common for AWS submissions. I don't mind a decent content marketing post that is supportive of Rust, but this one just rubs me the wrong way.
  - kbenson 6y ago
    > But the post is titled "How our AWS Rust team will contribute to Rust’s future successes", but doesn't actually say anything - at all. Maybe. I also think a case could be made that AWS coming out in support of Rust, and talking about how many products already use Rust and that they plan to have more is contributing to Rust's future success. Big companies/services like Amazon with AWS, Google with Compute or Microsoft with Azure stating how they are leveraging and making wide use of a technology provides a non-negligible boost to how that technology is viewed, whether they actually do anything or not.
nickm12 6y ago
Effective teams need a charter to understand who they are and what they do. Without this, they increase the risk that they thrash around trying to do all things for all people, or fail to take advantage of their unique talents and opportunities. This post gives the AWS Rust team's perspective about their charter, which is not at all vacuous. They are sharing with the community to seek earnest validation and feedback.

kbenson 6y ago

> No offense to Niko, but this is a completely vacuous post without a single concrete promise. Why does it need a promise? > I don't really see the point, except for PR, recruiting or internal signaling. It's messaging, sure. What's wrong with that? To me it looks like exactly what it says it is, communication regarding how they want to purport themselves in the community and what they're aiming for.

the_duke 6y ago
> communication regarding how they want to purport themselves in the community But the post is titled "How our AWS Rust team will contribute to Rust’s future successes", but doesn't actually say anything - at all. It's all just empty words without content. Apparently the mods agree, since the submission was downranked and blocked from the front page. Or maybe the algorithm picked up the odd upvote count and critical comment downvoting that is quite common for AWS submissions. I don't mind a decent content marketing post that is supportive of Rust, but this one just rubs me the wrong way.
- kbenson 6y ago
  > But the post is titled "How our AWS Rust team will contribute to Rust’s future successes", but doesn't actually say anything - at all. Maybe. I also think a case could be made that AWS coming out in support of Rust, and talking about how many products already use Rust and that they plan to have more is contributing to Rust's future success. Big companies/services like Amazon with AWS, Google with Compute or Microsoft with Azure stating how they are leveraging and making wide use of a technology provides a non-negligible boost to how that technology is viewed, whether they actually do anything or not.

nickm12 6y ago

Effective teams need a charter to understand who they are and what they do. Without this, they increase the risk that they thrash around trying to do all things for all people, or fail to take advantage of their unique talents and opportunities. This post gives the AWS Rust team's perspective about their charter, which is not at all vacuous. They are sharing with the community to seek earnest validation and feedback.