Live data from Hacker News

I refuse to let Amazon define Rust

twitter.com

271–280 of 363 posts

Re: I refuse to let Amazon define Rust

#271
post #247

Earlier quoted context omitted.

Here's hoping you finally get lambdas and destructors, and can step up.

Thanks for the feedback - I created a special issue tracker that gets higher priority, can you submit your proposal there? https://is.gd/WVZvnI

Or not, I guess.

I was, like Steve, rooting for you. Not so sure now...

Re: I refuse to let Amazon define Rust

#273

Well, if only Rust had a solid custodian, defender of open source... Oh wait, Mozilla basically ditched the project, and Servo, and Firefox OS... blame Mozilla.

The concern "A single organization shouldn't have too much power" did apply to Mozilla just as well.

Re: I refuse to let Amazon define Rust

#274
post #255

IDK I think this is overblown. Amazon employs two core members of Rust leadership. Both of whom worked hard on making Rust amazing like few others did. Both of whom who joined Mozilla to work on amazing projects for wages below what different places in the industry would pay. Do such people really betray their project of passion for money? Note that joining Amazon alone is no such act. It's joining Amazon and then be…

> It's joining Amazon and then becoming a heavy lobbyist for whatever Amazon wants to do with the language. To clarify, is that happening, or is that a warning that vigilance is needed to ensure it doesn't happen?

I meant it in the sense that it's not happening. But that if it happened, I'd be more worried. I think it would also fail.

The mere act of taking money, and Amazon presumably pays them a lot, is not immoral.

It only starts to be a problem if larger percentages of the teams work at Amazon, and people would be put onto teams just for being employed at Amazon. Linus Torvalds has made it clear that he doesn't make people maintainers for some component just for being employed somewhere. Instead of being bound to a company, maintainership is bound to the person. I think this is a good policy and one that Rust should keep.

Re: I refuse to let Amazon define Rust

#275
post #273

Well, if only Rust had a solid custodian, defender of open source... Oh wait, Mozilla basically ditched the project, and Servo, and Firefox OS... blame Mozilla.

The concern "A single organization shouldn't have too much power" did apply to Mozilla just as well.

I'll take Eich's era Mozilla over Amazon as a custodian of anything Open Source.

Re: I refuse to let Amazon define Rust

#276

Earlier quoted context omitted.

> 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. In another comment, Steve said he was not a member of the Rust Foundation: https://news.ycombinator.com/item?id=28514771

Your interpretation of "a group you are a member of" as referring to formal membership in the Rust Foundation specifically, rather than membership in the Rust community generally* seems like it gets at one of the issues in dispute, namely, whether there is an effort by corporate participants in the RF to (re)define what Rust is. (*): "community membership" is necessarily somewhat nebulous, but Steve is, undeniably, a…

Reminds me of the recurring debates we had (and have!) in KDE about the right way to structure decision making from the development community and the KDE e.V.

Re: I refuse to let Amazon define Rust

#277
post #273

Earlier quoted context omitted.

The concern "A single organization shouldn't have too much power" did apply to Mozilla just as well.

I'll take Eich's era Mozilla over Amazon as a custodian of anything Open Source.

The fact that you feel the need to specify an era is a pretty good sign the general concern does indeed apply.

Re: I refuse to let Amazon define Rust

#278
post #242
post #232

Earlier quoted context omitted.

Just based on the technology side: When using their systems a big thing, seems to be repackage and rebuild existing systems and create a load of new jargon. The systems seem to be islands, the effect is that at every place they are separated, billing can be introduced. Everywhere, where new names and jargon are introduced lock-in is introduced. I cannot see it being good for the medium or long term health.

So the worst case is Amazon makes the compiler or some tool or integration a paid service? Is paying for a well-maintained compiler a problem? Ada, Java, FORTRAN, and (I think) Julia all do this, right?

The only existing implementation of Julia in case that I know of is fully open source and MIT licensed.

It is well maintained and high performance :)

Re: I refuse to let Amazon define Rust

#279
post #21

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 sound…

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…

Agreed. Amazon might start off with good intentions, but it won't end nicely.

Re: I refuse to let Amazon define Rust

#280
post #37
post #21

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 sound…

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

AWS tenets are good inside of AWS. There is something oraclesque going on here.
Post reply on HN