Earlier 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…
I refuse to let Amazon define Rust
341–350 of 363 posts
Re: I refuse to let Amazon define Rust
#342Still don't know why we should let these big tech companies have board seats on programming language foundations for them to have the power to do this. I feared this would happen months ago when Facebook joined the board and even talked to steve about my concerns [0] [1]. Unfortunately it has come true with no surprise. [0] https://news.ycombinator.com/item?id=26125591 [1] https://news.ycombinator.com/item?id=2698928…
This really did not age well. There's a problem with this kind of absolute logical reasoning that it's impossible to argue against. "Sure this company has showed evil in the past, but what specific data do you have to show that they will be evil again?" "Sure this structure allows the company to have a lot of power, but what specifically makes you think they will abuse it?" This kind of specious reasoning is far too…
Re: I refuse to let Amazon define Rust
#343Ohhhhhhh, 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.
Nah Rust evangelism is pretty organic. I remember it having a cult 6 years ago too, before any of these companies got involved.
I'm sure it was. But it's six years on, and companies have gotten involved. They now have a financial stake. It would be naive to think that evangelism is still genuine grass roots, in the same way that it's naive to think the stuff on your FB feed reflects what your friends find interesting and worth sharing.
Re: I refuse to let Amazon define Rust
#344Earlier quoted context omitted.
FWIW these are not "Amazon employees that infiltrated the Rust ranks to take over". Mozilla fired everybody, and companies heavily invested in Rust like Amazon, Facebook, etc. hired them. So over night some people have labeled the opinions and work of these people as "Amazon opinions". Amazon has a lot of people working on improving Rust itself, and this gives them power, because they decide on what stuff the people…
Yeah of course, these are members of the community that were already contributing a great deal and just hired by Amazon. However, if Amazon is able to control the project and makes decisions for itself instead of the entire community of developers, that's a problem. My inexperienced opinion in OSS project management is leadership should be representative of the users and not cater to a subset.
Leadership is usually representative of merit, and merit comes from putting in the work.
Re: I refuse to let Amazon define Rust
#345Earlier quoted context omitted.
What is the issue with Mozilla being the patron of Rust? They are managing the Firefox project well. Would it be better if Rust was a part of the Apache foundation?
Apache is where projects go to die. So, probably not.
I thought that was CA? Oh wait, no, that's where they go after they're dead.
Re: I refuse to let Amazon define Rust
#346Google has Go, now Amazon has Rust, and Amazon will not let Rust go away. Amazon has enough money (and no moral or ethics) to take Rust and twist the reality to make people believe Amazon is right and Rust community is wrong. Let's watch the show.
But will Google let Go rust away?
Re: I refuse to let Amazon define Rust
#347Google has Go, now Amazon has Rust, and Amazon will not let Rust go away. Amazon has enough money (and no moral or ethics) to take Rust and twist the reality to make people believe Amazon is right and Rust community is wrong. Let's watch the show.
They're doing it now. Check out the flagged dead comments libeling Klabnik.
Re: I refuse to let Amazon define Rust
#348Earlier quoted context omitted.
So you're saying there isn't an issue with the Rust foundation's governance then? Now I'm assuming you just jumped into the comments without understanding anything no? EDIT: > We shouldn't be giving corporations too much power by letting them buy board seats in a foundation to steer the language, in this case Rust. @stale2002 I already mentioned this issue. However the user @secuthro22 continued trolling further with…
I wouldn't know. There might be, which is why I've asked you multiple times to explain the issue to me and yet you have neglected to do so.
Re: I refuse to let Amazon define Rust
#349Earlier quoted context omitted.
If you can't figure out what to be outraged about, maybe don't be outraged?
I'm not outraged at all. Where did you get this from? I was asking for details because everything has been very vague.
The fact that you're obviously trying to paint a legitimate worry as overwrought histrionics by spelling "worried" as "outraged" would seem to indicate you're already leaning towards the latter -- perhaps sufficiently so to be intentionally trying to ridicule the original worry.
Re: I refuse to let Amazon define Rust
#350Had to chime in on the first of the named "principles" of the language, because it makes a good example of what I think is wrong with the Rust community: > “Reliable: If it compiles, it works.” This isn't a principle. This is a subtweet. The principle being elucidated is something more like "fully specified semantics" or "no undefined behavior". And that's fine. But phrasing it like this is (1) obviously a lie as ple…
It's not just about UB, it's about the design encouraging good code and defensive programming. That includes enums, non nullability, immutability by default, etc.
AFAICS much -- if not most? -- of the stuff Rust is being lavishly praised for now already existed in Nikolaus Wirth's original Pascal from the early 1970s.