News for hackers. Stuff that matters.
Re:I refuse to let Amazon define Rust by kixiQu on Monday September 13, 2021 @12:31PM (#28513500)
Is there more context here that's missing from the tweet thread?

> And now they want to actually take Amazon's principles and claim that they're Rust's.

These just... literally... aren't Amazon's principles. At all. "The practice of coming up with pithy statements to guide decision-making" is the Amazon part.

> they've also taken steps to marginalize the core team. and some other dirty shit I won't say rn.

This sounds like the real concern, and it sounds really concerning, and I hope people come out to speak publicly and candidly about it. But it doesn't seem sensible to pretend that the making a list of adjectives is itself malign.

Re:I refuse to let Amazon define Rust by marricks on Monday September 13, 2021 @12:48PM (#28513689)
Steve Klabnik is well known in HN and in the Rust community, he mentioned it privately and doesn't seem to want to air dirty laundry more than he has too.

You can either see his history and trust that he wants to get as much done with as little said as possible or say you trust Amazon. Either is understandable but I think it's reasonable to be a known member of a community and speak up just enough to hopefully get the ball rolling in a better direction.

Re:I refuse to let Amazon define Rust by secuthro22 on Monday September 13, 2021 @01:13PM (#28513995)
>You can either see his history and trust that he wants to get as much done with as little said as possible or say you trust Amazon

Or I can trust neither, and expect that both sides act like adults and actually state their concerns and accusations rather than vague "just trust me, you should be upset" statements.

Whipping everyone into a furor with vague concerns without actually giving enough information to address those concerns is the worst form of "discussion", if you can even call it that.

Re:I refuse to let Amazon define Rust by marricks on Monday September 13, 2021 @02:13PM (#28514764)
He called out specific things and had a tweet which was pretty vague about some bad behavior. If you want to focus on that and imply it's childish you are the one distracting from discussing more important issues. That's probably why takes like that get downvoted.

---

From the comments Steve has made it sounds like Amazon effectively has control of Rust not only because of their large involvement but also because a strange set of governing circumstances. I guess I can see how if he led with that it might be clearer why all the concern, guess he didn't want to spell it out so directly and point fingers.

Re:I refuse to let Amazon define Rust by secuthro22 on Monday September 13, 2021 @02:27PM (#28514926)
He said in his first tweet that he wants to have a "serious conversation", then goes on to list three grievances: that Amazon has a lot of involvement in Rust leadership, that Amazon "marginalized the core team" (but no details) and that Amazon "has done some other dirty shit" (but no details).

That's two out of three grievances that have no substance whatsoever. You cannot have a serious conversation about these things if there is not more detail. I'm not distracting from anything, I'm asking Steve to either step up and discuss these things as he stated he wants to do, or he needs to stop distracting from serious issues with these snarky one-liners. If you include something like that in a tweet, you should expect to follow up on it.

It's ridiculous and disingenuous to tweet something like that and then say "well I don't actually want to talk about that and it's your fault for not reading my mind to know that".

>That's probably why takes like that get downvoted.

My comment currently has 50 upvotes. I don't think I'm the only person saying this.

Re:I refuse to let Amazon define Rust by vjust on Monday September 13, 2021 @05:51PM (#28517338)
Well he's one guy, against the industry behemoth. Give him some credit, rather than big brother. Even if he errs. I'd not buy any rebuttal by the thousand-pound gorilla at face value
Re:I refuse to let Amazon define Rust by marricks on Monday September 13, 2021 @03:14PM (#28515505)
I think you bring up good points and I was wrong saying it was only slightly unclear.

I don’t fault him as he didn’t post it here but it is definitely not fully clear from reading it what’s going on.

Re:I refuse to let Amazon define Rust by judge2020 on Monday September 13, 2021 @02:48PM (#28515165)
I think not adding details was a warning to Amazon to step up on their front or he will indeed 'air out dirty laundry', but it does feel disingenuous given we're asked to support him based on his word (and history of rustc contributions) alone.
Re:I refuse to let Amazon define Rust by kbenson on Monday September 13, 2021 @04:40PM (#28516593)
>> decided to not have a Rust Foundation ED, meaning Chair has outsized power in the Foundation

> that Amazon "marginalized the core team" (but no details)

That seems like details to me. It's also extrapolated on elsewhere here.

> That's two out of three grievances that have no substance whatsoever. You cannot have a serious conversation about these things if there is not more detail.

Actually, you could, just by ignoring the things you don't see evidence of and focusing on the points that do, and assessing them based on merit.

The messenger is irrelevant if the message is verifiable and is worth discussing. It's useful to call out points that seem to not be backed up, or be purposefully vague. It's not fine to use that as a reason to ignore other points because "you cannot have a serious conversation" when that's obviously not the case when it's not tried.

Re:I refuse to let Amazon define Rust by secuthro22 on Monday September 13, 2021 @06:53PM (#28517981)
>Actually, you could, just by ignoring the things you don't see evidence of and focusing on the points that do, and assessing them based on merit.

No, you really can't. Just by including the other points in the discussion, but being unwilling to extrapolate on them, shows bad faith (perhaps unintentionally) on the part of Steve and compromises the entire discussion. The only reason you include some vague "Amazon did shady shit" in a tweet is to elicit an emotional response on the part of the reader and immediately biases the argument against Amazon. The argument is not based on merit; it never can be now, because it's been tainted. This is known as "poisoning the well" [0].

Even in this thread, commenters are saying how they implicitly trust Steve not because of the merits of his argument, but because of his personal brand. He's (again, perhaps unintentionally) taking advantage of that fact by mud-slinging at Amazon, priming readers to already be biased against Amazon, and then once called out on it the response is "oh just ignore the fact that I did that and look at this other argument which I promise is more substantive". That's not arguing in good faith.

I see all that Steve has done for Rust and I see him post here (and on reddit) a lot, so I have respect for him. But this "discussion" was brought up completely the wrong way by him, and any outcome is going to be tainted. It'd be best to just let this current discussion die, and bring it up again in the future in a more appropriate manner.

0: https://en.wikipedia.org/wiki/Poisoning_the_well

Re:I refuse to let Amazon define Rust by kbenson on Monday September 13, 2021 @07:31PM (#28518266)
> Just by including the other points in the discussion, but being unwilling to extrapolate on them

That seems a bit strong. The statement was "won't go into rn (right now)".

> compromises the entire discussion.

It does. I'm not saying it causes no problems. I'm saying it shouldn't be grounds to immediately discount all other evidence given. It's perfectly valid as a modifier to another piece of evidence where you might use it to weight it, but I don't think it's valid to immediately ignore everything else said.

> The only reason you include some vague "Amazon did shady shit" in a tweet is to elicit an emotional response on the part of the reader and immediately biases the argument against Amazon.

No, that's one possible reason, it's not the only reason. Other possible reasons might be to signal other people more involved in the events in question that if they want to share their own story, perhaps now is the time and opening that makes that easier for them.

I agree that the presented argument would have been better without that statement, but that doesn't immediately negate the merit of what else is presented.

> The argument is not based on merit; it never can be now, because it's been tainted. This is known as "poisoning the well" [0].

The mistake you're making is in assuming that poisoning the well applies to and discredits non-dependent clauses. It should be easy to see how this applies when you consider the two statements "You should beware of John, he's made some threatening gestures to me and you in the past, and I there's been some assaults in the area" and "You should beware of John, he's threatening gestures to me and you in the past and multiple people have seen him assault three people recently." In one case it's used to imply guilt of something that is not factually proven or stated, in the other there's a fact to readily look into for confirmation that you can use as evidence to make up your own mind. That someone uses a call to emotion beforehand should not immediately discount that fact from consideration.

> Even in this thread, commenters are saying how they implicitly trust Steve not because of the merits of his argument, but because of his personal brand.

That's not what I've said, and not what I'm asking of you.

> But this "discussion" was brought up completely the wrong way by him, and any outcome is going to be tainted.

It may be tainted in some way. That doesn't mean easily verifiable facts should be ignored.

To be absolutely clear, since it seems very hard for some people to get my point, I have no qualms with your mistrusting him, or thinking his factual statements have no merit or are not problematic enough to act on. I just don't think it's valid to completely ignore the factual statements and refuse to consider them as you seemed to indicate you were doing because he also says "Amazon is being a meany in other ways too" and doesn't expound on it, and some other statements may not be as well supported as they could.

Re:I refuse to let Amazon define Rust by stale2002 on Monday September 13, 2021 @05:22PM (#28517049)
> and assessing them based on merit.

What merit? Lets take the claim of "marginalized the core team"?

WTF does that even mean? As in specifically, what was the action that amazon did, to marginalize anyone? Did they say mean things about them? Did they have a meeting without them? Did they kick them off of a group? Did they create a feature roadmap, without getting the core teams feedback?

Just say specifically what happened, with actual details, that describe exactly how someone was marginalize, and the consequences of that!

> reason to ignore other points

What other points? Specifically? The only verifiable point, that anyone has mentioned, is that amazon has a board seat somewhere, on some organization.

But even that point is low on details. Have they used the board seat to do anything bad? Whats the concern?

Re:I refuse to let Amazon define Rust by kbenson on Monday September 13, 2021 @05:33PM (#28517159)
> Lets take the claim of "marginalized the core team"?

You mean, "let's take an acillary claim, not one of the core three" that are stated to be "undefinable(sp). they're just facts."?

My point, which I thought was clear, but apparently not, is that if you have a problem with the statement you brought up, sure, mention that's problematic. But is that a reason to ignore the things mentioned immediately prior, that Amazon is the lead on multiple teams, and chose not elect a new executive directory while letting the prior one go? I think not. Those are specific claims that can be assessed individually. What bearing does the "they've marginalized the core team" statement have on them that renders them being unworthy to assess?

> What other points? Specifically? The only verifiable point, that anyone has mentioned, is that amazon has a board seat somewhere, on some organization.

That exact same tweet you reference notes they've decided not to have an Executive Director. Maybe if people weren't ignoring that because of some later statement that might get some attention.

Re:I refuse to let Amazon define Rust by stale2002 on Monday September 13, 2021 @05:43PM (#28517248)
> But is that a reason to ignore the things mentioned immediately prior

Its not ignoring! Its asking people to say what the actual problem is, beyond just that Amazon has people on a couple committees.

Have these committees done anything bad? Is amazon pushing for features that people don't like? Will some future bad thing happen because of this? What is the value statement here!

> Those are specific claims that can be assessed individually.

Ok, and the problem is that nobody is actually saying why some things are bad or not.

> that might get some attention.

I still don't know why it should get attention though. So they don't have an executive director? Why should anyone care?

You keep trying to say things, without saying why anyone should care about this stuff, or why it is bad.

I could make a dozen different guesses as to why you, or others, think there is a problem. But I shouldn't have to do that.

It is on you, to both say what is happening, as well as for you to say why it is bad, and what the concern is.

Re:I refuse to let Amazon define Rust by kbenson on Monday September 13, 2021 @06:22PM (#28517692)
> Its not ignoring!

Look a the comment I originally responded to. They complained that two out of three items had no substance, therefore we can't have a serious conversation. That is, specifically, what I was addressing.

> I still don't know why it should get attention though. So they don't have an executive director? Why should anyone care?

> You keep trying to say things, without saying why anyone should care about this stuff, or why it is bad.

It's specifically stated in the tweet. Not having an executive director leaves the chair with more power. Amazon is the chair. Amazon has chosen to let the position go unfilled which results in their own position having more power.

He goes into more detail here: https://news.ycombinator.com/item?id=28513656

Actually asking questions about that, like you are here, is the outcome I was calling for, as opposed to ignoring it because of other statements, as the original comment I replied to was.

> It is on you, to both say what is happening, as well as for you to say why it is bad, and what the concern is.

No, you're placing me as someone on the one side of the argument, when the side is irrelevant. My point was that ignoring everything said because of portions that don't add up is not a valid way to assess the information. That doesn't require me to take a side, and in fact taking a side just makes it easier to people to dismiss my point and assume my goal is something else, as I suspect you did.

Re:I refuse to let Amazon define Rust by stale2002 on Monday September 13, 2021 @06:42PM (#28517862)
> in fact taking a side just makes it easier to people to dismiss my point

The problem is that, it is pretty clear, that based on how many people have agree with me, that this guy was unclear.

There was obviously a lot of confusion here. And that is a valid criticism of this person.

> My point was that ignoring everything said

The fact that so many people are confused about what the guy is saying, is on him.

He should have communicated better. And no, it is not everyone else's fault, that basically everyone misunderstood his point.

> He goes into more detail here

Well maybe he should have done a better job of communicating his ideas, from the very beginning. That's on him.

The fact that he was so bad at saying what the problem was, and why we should care, from the very beginning, is a valid problem.

> is not a valid way to assess the information.

No, it is not on the public to have to cross reference hacker news posts, with tweets, with blogs posts, to figure out why we should care.

That is the job of the communicator. And if you communicate it poorly, then that is your failing.

Re:I refuse to let Amazon define Rust by kbenson on Monday September 13, 2021 @06:56PM (#28518002)
You continue to ignore the point I'm making and the context I made it in, in what appears to be an effort to push your own agenda. You can feel free to to that, but I don't see a reason to continue my part in this conversation when it feels like you're not attempting to actually engage with me.

If you care about why I think it's not worth continuing, and why I've come to this conclusion, I suggest you attempt to re-read what I wrote previously with a more open mind and instead of trying to drag it back into the specific argument. In any case, have a good evening.

Re:I refuse to let Amazon define Rust by stale2002 on Monday September 13, 2021 @07:14PM (#28518139)
Dude, even in the post that you linked, where you claim that he "goes into more detail", he is missing the main value judgement punchline.

The summary of that statement is "During that time, the chair of the board has more power than they usually would, and Amazon is chair of the board."

But once again, he is refusing to give the actual, moral punchline here.

If he wanted to convince people, he could explain all the dastardly things that he believes the board could do now. But he doesn't do that. All he says, is another statement that is devoid of moral argument, which is that "amazon is chair of the board" and that the board has more power.

The way to actually make an argument, is to not simply state facts. Instead you should say why people should care about these facts, and describe the actual material harm.

> , but I don't see a reason to continue my part in this conversation

Yes, I get it. When someone brings up the fact that basically everyone is pretty confused about the situation, and brings up how poorly this guy communicated, you have no response, and just want to assert you that you disagree, without backing it up.

Re:I refuse to let Amazon define Rust by LanceH on Monday September 13, 2021 @01:43PM (#28514363)
I said something similar and got downvoted. I should have been more clear that posting this to HN as though it is meaningful is the problem.

There is no substance to the tweets (it's his twitter account, go wild), and really has no business being here.

Re:I refuse to let Amazon define Rust by PragmaticPulp on Monday September 13, 2021 @01:00PM (#28513825)
> he mentioned it privately and doesn't seem to want to air dirty laundry more than he has too.

Unfortunately, it seems we're getting the worst of both worlds: The dirty laundry is being aired in this thread, but the actual details are being withheld.

From the Tweet thread:

> they've also taken steps to marginalize the core team. and some other dirty shit I won't say rn.

I'm not a fan of these "just trust me" accusations.

Re:I refuse to let Amazon define Rust by rualca on Monday September 13, 2021 @01:36PM (#28514273)
> I'm not a fan of these "just trust me" accusations.

Feel free to disregard the trailing sentence. However, it's not fair do discard each and any substantiated accusation by trying to shift the attention to a passing comment, specially a common one which is used as a figure of speech.

Re:I refuse to let Amazon define Rust by ipaddr on Monday September 13, 2021 @12:55PM (#28513771)
Because he is well known many will listen.

The not airing dirty laundry and not detailing the issue means no one knows what is going on and no one can help.

If it's a private fight I would understand if they wanted to keep it private. If it's a public issue what is happening.

Re:I refuse to let Amazon define Rust by dmix on Monday September 13, 2021 @01:19PM (#28514086)
This is one of my pet peeves on social media. Nothing is worse than vague references to personal issues or something requiring inside knowledge, while the person refuses to elaborate (not saying this is true here, I haven't dug into this issue). If you're going to make it public, decide to actually make it public.
Re:I refuse to let Amazon define Rust by type0 on Monday September 13, 2021 @06:43PM (#28517875)
He could have expressed his concerns in a coherent blog post, that maybe could have sprawled a more serious discussion, we all know he's a good writer. Choosing to do this in a series of tweets tells just one thing - "nothing of substance here, move on".
Re:I refuse to let Amazon define Rust by sergiomattei on Monday September 13, 2021 @01:15PM (#28514033)
More than he has to? Dude already named names. Cat's out of the bag, might as well go all the way.
Re:I refuse to let Amazon define Rust by vjust on Monday September 13, 2021 @06:13PM (#28517576)
Agreed. Amazon might start off with good intentions, but it won't end nicely.
Re:I refuse to let Amazon define Rust by refenestrator on Monday September 13, 2021 @01:35PM (#28514270)
Either air dirty laundry or don't, then. "They are super shady, trust me" is worse than both.
Re:I refuse to let Amazon define Rust by ilaksh on Monday September 13, 2021 @01:40PM (#28514335)
I assume that Amazon getting too much control is a real problem. But also suspect that deep down the true concern Klabnik has is that Steve Klabnik thinks Rust is about him, or at least he is the one that is supposed to write articles about what Rust is about. Not someone from Amazon or anywhere else.
Re:I refuse to let Amazon define Rust by steveklabnik on Monday September 13, 2021 @01:47PM (#28514403)
I do not think Rust is about me. Note that I specifically say that Rust should not be about any individual, let alone a company. I’ve made my case against BDFLs for years.
[dead]
Re:I refuse to let Amazon define Rust by steveklabnik on Monday September 13, 2021 @02:04PM (#28514642)
One of my favorite aspects of the way the Rust community has acted over the last decade is to recognize that there are many ways to contribute to open source. I know not everyone feels that way. Luckily, since I don't want Rust to be about me, we're in agreement that I should not be in charge of Rust.
Re:I refuse to let Amazon define Rust by Animats on Monday September 13, 2021 @04:09PM (#28516174)
That is a problem. Perl 6 and Python 3 did not go well.
Re:I refuse to let Amazon define Rust by type0 on Monday September 13, 2021 @06:46PM (#28517905)
> But also suspect that deep down the true concern Klabnik has is that Steve Klabnik thinks Rust is about him, or...

Oh, don't post this kind of personal attacks.

Re:I refuse to let Amazon define Rust by ilaksh on Monday September 13, 2021 @10:40PM (#28519570)
It's not a personal attack. It's just a theory. There was nothing substantive in the article.
Re:I refuse to let Amazon define Rust by mnk47 on Tuesday September 14, 2021 @05:03AM (#28522067)
There was nothing substantive in the article because it got edited soon after his tweet. https://web.archive.org/web/20210913110658/https://www.infow...
Re:I refuse to let Amazon define Rust by stjohnswarts on Tuesday September 14, 2021 @02:10AM (#28520894)
He's pointing out big changes coming to control of the Rust foundation and positing that Rust foundation being controlled by one large single corporate entity probably is not a good thing. Nothing in there seemed to me like he wanted to be the one in control.
Re:I refuse to let Amazon define Rust by mjw1007 on Monday September 13, 2021 @12:40PM (#28513601)
The announcement blog post at https://smallcultfollowing.com/babysteps//blog/2021/09/08/ru... says the initial version was "quite closely modeled on AWS tenets".
Re:I refuse to let Amazon define Rust by cwp on Monday September 13, 2021 @01:07PM (#28513924)
As the GP says, this probably refers to the practice of having short pithy statements to guide decision making. That is, AWS uses "Tenets" to help guide their decision making, Niko found that useful and wanted to do the same thing for Rust.

The post you linked to above links to a YouTube video[1] where he describes where the principles came from: some "design tenets" he came up with to help guide design of the async feature in Rust. Later he realized that they weren't specific to the async work, but were more about Rust in general. There has since been a lot of iteration involving others in the Rust community, and he's no longer calling them tenets.

And really, if you actually read the principles themselves, do they really sound like they're based on the design tenets that AWS uses? They sound an awful lot like principles that the Rust community has been using, but never articulated before. Maybe some more iteration is necessary, but it doesn't look very sinister.

[1] https://www.youtube.com/watch?v=ksSuXNmGZNA&t=2001s

Re:I refuse to let Amazon define Rust by oxymoron on Monday September 13, 2021 @12:57PM (#28513792)
Tenets as used internally at AWS are a set of principles that each team decides for themselves, as guides in the face of ambiguity. There's no overarching set of tenets (that I'm aware of), so this is probably just referring to the idea of having a guiding set of principles to resolve tradeoffs.
Re:I refuse to let Amazon define Rust by whoknew1122 on Monday September 13, 2021 @01:28PM (#28514188)
This. Each org, team, and project has their own set of tenets. There are a few common sense tenets that are overarching (Security is priority 0), but there is no one set of 'AWS tenets.'

Tenets are used as quick statements to validate decisions. And the tenants are always up for debate and revision.

Using 'AWS tenets' isn't some nefarious way to control Rust. It's borrowing a useful (IMO) management/decision making structure to help guide decisions. Using 'AWS tenants' doesn't give AWS undue influence anymore than using the concept of Andon cords gives Toyota undue influence.

Re:I refuse to let Amazon define Rust by fsociety on Monday September 13, 2021 @02:59PM (#28515320)
I disagree a lot. I don’t think using AWS Tenets was done nefariously.. but it has an important implication on the Rust community as a whole.

Engineers are really relying on the Rust Foundation to do right by them, and by adopting Amazon or other big tech company principles it’s spitting in the face of engineers who don’t trust them and adding the potential for bias in decision making of the foundation.

I’m hopeful that the Amazon contributors will understand this and show full support.

Re:I refuse to let Amazon define Rust by whoknew1122 on Monday September 13, 2021 @03:08PM (#28515438)
Again, Rust hasn't adopted Amazon's principals. It has adopted a mechanism used by Amazon by which it can define its own principles.

The tenets of the team I work on are stuff like 'treat every customer like your best friend on their worst day'. And 'learn something new every day'. They are tenets of a team in AWS, which makes them (to some extent) 'AWS tenets'.

Are they somehow nefarious because there are people who don't trust anything that remotely relates to Amazon? Or are they innocuous statements of intent that are applicable to most companies?

You don't have to like or trust Toyota to use Andon cords. You don't have to like or trust McKinsey to use the 7-S framework. You don't have to like or trust Motorola to use Six Sigma. You don't have to like or trust Amazon to use 'AWS tenets'.

Re:I refuse to let Amazon define Rust by fsociety on Thursday September 16, 2021 @02:31PM (#28555344)
Right and now we are in semiconductor shortages because people adopted Toyota concepts in a non-Toyota context. In the mean time, Toyota adapted their own concepts to weather the storm of semiconductor shortages, for a short while atleast.
Re:I refuse to let Amazon define Rust by HowTheStoryEnds on Tuesday September 14, 2021 @01:36AM (#28520638)
No, but you do have to trust said tenets and their application.
Re:I refuse to let Amazon define Rust by nickm12 on Monday September 13, 2021 @04:57PM (#28516786)
This is a misunderstanding. Amazon and AWS use "tenets" as a tool for focusing and aligning a team on what it values. The Rust Principles are an application of that tool for the Rust project, not adopting the exact same tenets that teams at Amazon/AWS use. See this 90 second video for a quick rundown of how tenets are used.

https://www.youtube.com/watch?v=5raEKA57PMY

(Disclosure, I'm an Amazon employee and am familiar with how Amazon uses Tenets for teams)

Re:I refuse to let Amazon define Rust by vjust on Monday September 13, 2021 @06:17PM (#28517622)
AWS tenets are good for AWS. Rust has its own tenets. Both should be kept separate.
Re:I refuse to let Amazon define Rust by nickm12 on Monday September 13, 2021 @08:00PM (#28518471)
Yes, that is exactly what is happening here! When the Rustacean Principles were created, Niko said in his blog post[1] that the idea of creating principles was inspired by AWS. Not that the principles themselves were taken from AWS.

Writing tenets is a tool, like making a checklist is a tool. You can use the idea of making a checklist without using the checklist items.

[1] https://smallcultfollowing.com/babysteps/blog/2021/09/08/rus...

Re:I refuse to let Amazon define Rust by vjust on Monday September 13, 2021 @06:16PM (#28517612)
AWS tenets are good inside of AWS. There is something oraclesque going on here.
Re:I refuse to let Amazon define Rust by benatkin on Monday September 13, 2021 @12:39PM (#28513592)
Re:I refuse to let Amazon define Rust by thrwn_frthr_awy on Monday September 13, 2021 @02:29PM (#28514939)
>> they've also taken steps to marginalize the core team. and some other dirty shit I won't say rn.

> This sounds like the real concern

I actually think it distracts from their argument. Either say something or don 't. What purpose do vague accusations have here? Scare Amazon into behaving so not to get bad press? If the actions are concerning enough that Amazon should not have full-control, then why wouldn't those actions still not be pertinent if they do not define Rust.

Re:I refuse to let Amazon define Rust by Ansil849 on Monday September 13, 2021 @12:35PM (#28513544)
> Is there more context here that's missing from the tweet thread?

When is there not? Tweets are a horrible medium for contextual information.

Re:I refuse to let Amazon define Rust by LanceH on Monday September 13, 2021 @12:46PM (#28513669)
Incredibly vague rants are designed to get people to take sides, presumably against Amazon, because they're big and therefor always doing evil.

This reads like drama for the sake of drama.

Edit: I should have said that posting this to HN is just posting drama. Using twitter to vent is fine, just not newsworthy in any way.

Re:I refuse to let Amazon define Rust by stjohnswarts on Tuesday September 14, 2021 @02:14AM (#28520923)
Uh it is newsworthy. This isn't Kim K tweeting about a particularly painful hangnail. It has some serious ramifications for the future of Rust if Amazon is becoming too powerful in the community.
Re:I refuse to let Amazon define Rust by SloopJon on Monday September 13, 2021 @12:50PM (#28513723)
The first tweet links to an InfoWorld article (pseudo-paywall and many ads):

https://www.infoworld.com/article/3633002/the-future-of-rust...

Steve is probably objecting to the paragraph that starts, "Given that Matsakis and Miller both work at AWS, it's not surprising that the [Rustacean] principles started out as a spin on Amazonian tenets."