Live data from Hacker News

Why I Left Rust

jntrnr.com

121–130 of 880 posts

Re: Why I Left Rust

#121

I love Rust but the ideological posturing and swathes of people who in their hearts are grifters is truly disappointing. Framing a technical presentation you disagree with as "making you uncomfortable" in highly manipulative fashion definitely deserves to be called out in public.

I couldn't agree more. This is pure manipulation.

Re: Why I Left Rust

#122

I once got a talk demoted from a normal talk to a lightning talk at some unrelated conference to make it work with the schedule. That was indeed not nice. But also not "Cruelty". I just acted professionaly and accepted the change.

Melodrama from the blog post aside, publicly downgrading a talk for an industry wide conference is very much a slap to a speaker's face.

"Hey we think you have great ideas to share, and would really like you to share them."

On short notice: "One of our team members thinks your ideas aren't that important after all, we are going to remove you from the headline. Please keep it short kthxbye."

It shows bad planning, bad organization, lack of cohesion, and outright disrespect of your professional time. You may choose to accept that slap to your face (signaling that it's okay to do that to you), but there's nothing unprofessional about rejecting the attendance and rightfully criticizing the organizers for their rudeness.

Re: Why I Left Rust

#123
post #115

Earlier quoted context omitted.

Is it bad of me to say I really just don’t care? If he did the talk. If he did it as a keynote. If someone else is “leaving rust” because of it? It all seems so fabulously irrelevant, I really struggle to understand why: 1) I should care (I don’t, currently) 2) People are coming out of the woodwork to criticise the rust team / foundation whatever when they’re not involved. 3) Why people having emotions (eg. The perso…

From my understanding the Rust team was involved and they sidestepped democratic processes put in place to make sure the Rust foundation doesn't kill itself with unchecked mismanagement essentially. The point is more that this sort of unilateral decision should never have been possible to make in the first place. It should have been discussed and voted on before the talk was downgraded. Perhaps that specific incident…

How? Everything is done openly on https://github.com/rust-lang/rfcs

I mean, I hear you. I understand what you're saying, I just don't understand how you (or others) think this is related to the technical aspects of the language.

Re: Why I Left Rust

#124
It looks like JeanHeyd is unwittingly used as a weapon in a conflict internal to the Rust leadership. It look to me as an escalation of the conflict : - First, a power move to invite someone outside of the community that have a strong point of view on a technical subject. As any organisation, you have to make move to make your agenda move forward. - Second, an escalation with the uninvite. Not polite, but asserts the power you have within the organisation. - Third, a resignation with a strong post that is another level of conflict.

What will happen next ?

Re: Why I Left Rust

#125
post #10

I've been to plenty of conferences over the years, and I never really knew who was a "keynote speaker" or "only" a "speaker". Does anyone pay attention to this? You give a talk. People show up. They clap at the end. Does it really matter what some title on some conference website is? The communication was perhaps a bit more confusing and hectic than it should have been, but does that really matter? Is that really a b…

This reasoning makes no sense. If keynote and a regular talk are not meaningfully different why did Rust leadership switch it?

If it's purely ego then there are even more serious concerns if ego dominants an entire conference organising committee then withdrawal was the only reasonable option.

For the uninitiated, a keynote sets a theme and tone for a series of talks.

Usually it's less technical and more personal than later talks. Explaining the significance of the topic that will be discussed in upcoming talks.

Re: Why I Left Rust

#126
post #115

Earlier quoted context omitted.

From my understanding the Rust team was involved and they sidestepped democratic processes put in place to make sure the Rust foundation doesn't kill itself with unchecked mismanagement essentially. The point is more that this sort of unilateral decision should never have been possible to make in the first place. It should have been discussed and voted on before the talk was downgraded. Perhaps that specific incident…

How? Everything is done openly on https://github.com/rust-lang/rfcs I mean, I hear you. I understand what you're saying, I just don't understand how you (or others) think this is related to the technical aspects of the language.

Because the same people are involved, and they knowingly sidestepped these exact sorts of processes without care. It might not be important to you, but this seems like a red flag to many.

Re: Why I Left Rust

#127

I've attended a few Rust conferences and events, and they have all been unusually politicized. There has been a very strong emphasis on how inclusive the community is, which raises some red flags. It is akin to someone repeatedly expressing how smart or funny they are... it makes you wonder why. I was waiting for something like this to happen.

I agree. I've been scolded before by saying how unwelcoming the "Rust community" can be, and everyone comes out of the woodwork to say how inclusive it is. They're not the same thing. All of this is childish drama, around a _programming language_. Strange...

Re: Why I Left Rust

#128

I haven't seen anyone bring this up, so I will. I read through the original blog post from JeanHeyd[1] and in no way do they mention anything related to being a person of color, why then does JT associate it with that? I have no idea about the inner workings of the rust leadership team and who they are even, but from the timeline described and from the original post, there's nothing the could be related to that. Jean…

I think moreso than specifically meaning JeanHeyd was target as such due to race, the implication was rather that since JeanHeyd had previously raised that the lack of diveristy in speakers at the conf. was an issue, some members voting on this may have held onto that.

But, it's ironic (and sad) that the same person who raised the issue of diversity in speakers - who would have been the first PoC doing a keynote - was treated like rubbish and essentially pushed out to the point they no longer feel comfortable being part of it at all. It's also interesting to note that while the issues the voting body had with their talk was solely to do with the content of the talk, it begs the question of if any other participant would be treated the same way in dealing with that issue arising. In my experience it's not uncommon for that sort of irony to play out, but that's purely anecdotal.

Also, of course white is a colour but I've always seen PoC as a slightly more language-open alternative to the previously commonly used "non-white" which feels notably like language from an era long past.

Re: Why I Left Rust

#129

How does this kind of organizational drama affect me as an end user of the Rust programming language?

It doesn't and shouldn't. The people in the Rust project will come and go, but the language will continue to be developed. Many contributers are not project members

Re: Why I Left Rust

#130
post #77

Wait. Let me get this straight. Someone is an expert in this field. They're asked to speak at RustConf after a leadership vote. They've also written an article about reflection in Rust - a purely technical thing that is already pretty widely disliked conceptually. (EDIT: the talk was about this, but it's also compile time reflection and came with the usual disclaimer that it was not representative of any of the Rust…

Compile-time reflection is great in principle. It gets us quite close to the aim of compile-time dependent types, which would be a great feature for Rust and bring it close to parity with newer languages such as Zig, as well as lay the groundwork for further important developments such as proof-carrying code. It would be quite important to know why this Rust team member felt "uncomfortable" with the technical contents of this talk which were clearly described by the author as highly speculative, and thus inherently open to discussion.
Post reply on HN