Live data from Hacker News

I refuse to let Amazon define Rust

twitter.com

141–150 of 363 posts

Re: I refuse to let Amazon define Rust

#141
>I want big companies to be involved in Rust

Why?

Steve Klabnik is one of my favorite technical writers. He is also an anti-capitalist. Early Rust documentation contained a lot of references to influential 20th century Marxists like Rosa Luxemburg.

I feel people like him should increasingly stand their ground instead of being apologetic about their views.

Re: I refuse to let Amazon define Rust

#142

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…

Hey Steve! Forgive me if you already have touched on this, let me know and I can do more digging myself, but upon expiration of Ashley's contract as ED, you said it was the foundation that decided to not extend her contract. Would that have be the group decision including each member director or solely the chairwoman's?

I am not an expert in the foundation's bylaws, and the only thing they said publicly is "The Rust Foundation Board of Directors also wishes the best to Ashley Williams, who will be leaving the post of interim executive director "[1].

I expect that it was a group decision and not a sole one. But again, my point is not about how that happened, my point is that it has happened, and what that means for the state of the organization as a whole, that is, that leadership is concentrated in a single organization.

1: https://foundation.rust-lang.org/posts/2021-06-25-announcing...

Re: I refuse to let Amazon define Rust

#144
post #90

Earlier quoted context omitted.

Rust isn't the only community that's at risk of getting coopted by corporate sponsors. The PostgreSQL core team now has an explicit policy that no single company employs more than half its members -- but to follow it, last year, they had to expand membership (after companies employing 50% of the prior core team merged, and they didn't want to boot anyone). https://postgresql.fund/blog/is-it-time-to-modernize-postgre.…

Oddly enough, the post you linked to is from the blog of Fundación PostgreSQL, which is also being discussed on HN today due to a dispute with the PostgreSQL core team: https://news.ycombinator.com/item?id=28512274

Charming. Just grabbed the first link that described the issue. But yeah, the Spanish organization seems... confused at best regarding its own role.

Re: I refuse to let Amazon define Rust

#145

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 don't want Amazon to define Rust but I want my pal to define it doesn't exactly sound like a solid argument. Is there any more meat on the bone here?

That’s a ridiculous interpretation of what was said.

“There are 2 entities which make decisions...the contract for the person holding the post of 1 of those 2 entities was not extended by the other entity, and the other entity has not given any timeline on when they expect to fulfill that position, therefore leading to a situation where it’s the only entity with power” is not “I want it run by my pal”.

Re: I refuse to let Amazon define Rust

#146
post #138

I actually really like Zig's stance on this. Not having company members on the Board + trying to employ developers from the community helps with the issues that Rust is currently facing. Of course due to Rust's history things work differently, but hopefully Steve's comments will get them to look at this issue more critically

I guess this is one of the benefits of having the language direction owned by a single author - they might feel a bit more empowered to make this kind of principled stance in the face of strong incentives to trade funding for corporate guidance.

Sure, but we're not just doing things out of principle. We have a clear plan on how to be sustainable without giving up seats. It's not all sunshine and rainbows, there are some compromises to make, but we know what we want and what we're willing to give up in exchange.

I wrote a while ago my thoughts here:

https://kristoff.it/blog/the-open-source-game/

Re: I refuse to let Amazon define Rust

#147
post #127

Earlier 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.

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.

Rust certainly cannot be “about” one person who has made zero technical contributions to the language.

Re: I refuse to let Amazon define Rust

#148
Had 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 plenty of Rust code will compile that doesn't work and (2) needlessly picking a fight with C/C++ instead of engaging productively in a discussion of tradeoffs.

Meh. It's time for Rust to start doing more and saying less, IMHO.

Re: I refuse to let Amazon define Rust

#149
I think Steve has a well earned reputation for being decent and trustworthy.

I can understand the desire here for more details so that others can come to a firmer conclusion but try to put yourself in Steve's shoes. It is very hard to publicly criticize some of the behavior of a group you are a member of without burning bridges or deeply harming relationships. At the same time, saying nothing publicly is read as tacit approval.

I interpret the article as a giving Amazon credit for why people like Rust, and Steve's response as a public disagreement saying that such credit is unwarranted and gives Amazon more power than it should have over Rust's future direction.

Re: I refuse to let Amazon define Rust

#150
post #90

Earlier quoted context omitted.

Rust isn't the only community that's at risk of getting coopted by corporate sponsors. The PostgreSQL core team now has an explicit policy that no single company employs more than half its members -- but to follow it, last year, they had to expand membership (after companies employing 50% of the prior core team merged, and they didn't want to boot anyone). https://postgresql.fund/blog/is-it-time-to-modernize-postgre.…

It's worth noting that this has been an informal rule for over 20 years, the organisations in question are Postgres specific specialists and the developers in question have long histories with the project. I don't think it's quite the same to be honest.

the situation is not the same, but the familiar corporate pressures expected to emerge and the reasons for the rule are the same: it bears scrutiny and oversight. If an erosion of trust in a group like this is not something to worry about, what is?
Post reply on HN