Earlier quoted context omitted.
> she just might not have wanted to become chairwoman of the foundation. I can assure you she would have been happy to continue to be the executive director. I talked about this briefly in the thread, but wasn't quite clear enough, so might as well also elaborate here, since it was brought up. I am not worried that she will not be the next ED. I mean, I would have preferred it, but it's not my decision to make. The s…
I see now what this is truly about.
I refuse to let Amazon define Rust
321–330 of 363 posts
Re: I refuse to let Amazon define Rust
#322Earlier quoted context omitted.
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.
> 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
#323Re: I refuse to let Amazon define Rust
#324Hey, at least they didn't pick "move fast and break things" as a core principle. They're doing better than C/C++.
Rust is just a single implementation that's CI'ed with nightly releases.
Re: I refuse to let Amazon define Rust
#325Ohhhhhhh, this explains a lot of the "Rust is the next great thing" I keep seeing around. Amazon has taken a page out of Microsoft's 90s playbook of embracing stuff and astroturfing their extensions until they claim it as their own and extinguish competition. I hope the Rust team finds a way out, but I suspect now that if Amazon has their hooks in it then they'll just fork it.
Re: I refuse to let Amazon define Rust
#326Earlier quoted context omitted.
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 t…
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…
Re: I refuse to let Amazon define Rust
#327Earlier quoted context omitted.
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 th…
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
#328Earlier quoted context omitted.
> Is there more context here that's missing from the tweet thread? When is there not? Tweets are a horrible medium for contextual information.
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
#329Earlier quoted context omitted.
When ISO C++98 came out there was no Google, or better said, it was just been founded.
You are correct. I may have read more into GP’s post than they intended. I assumed given the issues present in the tread and the original tweets, I assumed they were referring to the Committee submission document from 2020 [1] and the ‘uproar’ from non-FAANG developers. 1 - http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p213...
Re: I refuse to let Amazon define Rust
#330The Rust Foundation has indeed been disappointingly opaque. Their website contains only anodyne director bios and board meeting minutes. The minutes go up to May's meeting, with most of the content omitted under a "Private Session" heading. AIUI the main need for a foundation was so they could own the Rust domain names and trademarks. Eight months later, I've seen no announcement on whether any progress has been made…
I don’t actually see how Amazon stewardship is a bad thing. Corporate custody has been the case for several useful programming languages, with Java, .NET, and Go being obvious and popular examples. Replacing a core team of advocacy-oriented developers with production-oriented developers might give the project a positive new direction too. After all, a popular, design-by-committee compiled language with RAII memory ma…