News for hackers. Stuff that matters.
Re:Results of Rust Survey 2016 – early draft for internal usage by akerro on Thursday June 23, 2016 @04:09AM (#11959497)
Thanks for your work guys. I took part in the survey when I found it on Reddit. Yesterday I started my first project in two new technologies, Rust and GTK. That's completely different experience and perspective of designing code after years of C++(Qt) and Java(backend). Now I wish I was earlier adopter :)
Re:Results of Rust Survey 2016 – early draft for internal usage by Manishearth on Thursday June 23, 2016 @06:08AM (#11959863)
Thank you! I'd love to hear more about your experience, though perhaps once you have worked a bit more on the project :)

Eh, early adoption is overrated -- you have to fight through lack of docs, lack of libraries, and general ecosystem issues, all while the language keeps changing underneath you :P

(Note that not everyone who works on Rust; or even who worked on this survey, is a guy)

Re:Results of Rust Survey 2016 – early draft for internal usage by akerro on Thursday June 23, 2016 @07:04AM (#11960105)
> I'd love to hear more about your experience

I had good experience integrating glade (GTK GUI generator) to Rust, but bad experience with getting auto-complete working in Eclipse, in fact it's still not working ;) It's a pain when I using new technologies (both Rust and GTK are new to me). I want to change its state from `checked` to `unchecked`, and I don't know what's name of the method that does it, it can be setState(bool) setChecked(bool), setEnabled(bool), setActive... you know what I mean, the method is there, but checking docs just to get method name is annoying. I'll try it in vim later today.

My goal is to write (simple) desktop sharing application. Any thoughts how hard can it be? I need OS-integration, ffmpeg to catch screen, integration with decoding video stream without bloating systems...

Re:Results of Rust Survey 2016 – early draft for internal usage by Manishearth on Thursday June 23, 2016 @07:55AM (#11960272)
> I'll try it in vim later today.

I use YouCompleteMe with vim, which works for many editors as well as many languages. Though I recently switched to a mac and the sublime plugin is broken :/

> Any thoughts how hard can it be? I need OS-integration, ffmpeg to catch screen, integration with decoding video stream without bloating systems...

Shouldn't be too hard. Rust certainly won't stand in your way, but I'm not aware of how hard some of these things may end up being :)

Re:Results of Rust Survey 2016 – early draft for internal usage by fiedzia on Thursday June 23, 2016 @06:31AM (#11959949)
Note that many people use the term "guy" without relation to sex or even being a person.
Re:Results of Rust Survey 2016 – early draft for internal usage by Manishearth on Thursday June 23, 2016 @06:44AM (#11960009)
I know. I'm not questioning the intention, I'm requesting the term not be used that way -- it is known to alienate people.
Re:Results of Rust Survey 2016 – early draft for internal usage by adrusi on Thursday June 23, 2016 @08:35AM (#11960411)
Communication is a two-way street. A polite speaker has to take into consideration how their audience wants to be addressed, but polite listeners need to take into consideration that the speaker's words are the speaker's. My autistic brother will get very anxious when he anticipates a specific phrase in response to something but the person words it differently from how he expects, and he then insists that the person repeat the phrase with the "correct" version. The motivation is different from blind political-correctness, but the crime is the same. Words are symbolic of experience, and even though we all generally agree on what words mean, different people associate them with different experiences, so they essentially have reimplementation of the same word. Why should one person have to fully accomodate one person's implementation of "guy" while the other person just ignores what they know the first person means by that word?
Re:Results of Rust Survey 2016 – early draft for internal usage by alienated on Thursday June 23, 2016 @10:03AM (#11960888)
> it is known to alienate people.

So is language policing.

The Rust Code of Conduct [0] states:

Don’t just aim to be technically unimpeachable, try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they’re off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely.

You've brought up something off-topic (and potentially sensitive) when there was no real need, and definitely no ill-intent in the original - and just like the code of conduct predicted, it's already starting to develop in to unnecessary bickering.

This sort of language policing is exactly the type of thing that can drive people away from a community - and was not really necessary in the original context.

As per the Rust Code of Conduct the correct response would have been:

if someone takes issue with something you said or did, resist the urge to be defensive. Just stop doing what it was they complained about and apologize

Now, before you go on to defend yourself, the CoC further states:

Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could’ve communicated better

And that's something worth considering.

Now, I know that the Rust Code of Conduct states that it is only enforced on official Rust venues, and so there is no expectation of you following it here on HN, but as a respected member of the Rust community I would hope it was something you would still follow in a public forum, out of respect for what it stands for.

[0] - https://www.rust-lang.org/conduct.html

Re:Results of Rust Survey 2016 – early draft for internal usage by kbenson on Thursday June 23, 2016 @10:58AM (#11961405)
You know, if you feel the need to make an account to post what amounts to a rules lawyering comment to what you perceive as a language police comment, perhaps you're taking the wrong approach. There are less blunt methods.
Re:Results of Rust Survey 2016 – early draft for internal usage by alienated on Thursday June 23, 2016 @11:14AM (#11961577)
You are right, and I apologize.

It was done to belabor a point. Namely that for a community that aims to be welcoming, belaboring that point can actually make it less welcoming.

It is taxing to participate in an environment where common language usage causes people to take offense where none is given or intended.

Re:Results of Rust Survey 2016 – early draft for internal usage by carols10cents on Thursday June 23, 2016 @11:26AM (#11961704)
Using the word "guys" to describe Rust developers is not offensive; it's just incorrect.
Re:Results of Rust Survey 2016 – early draft for internal usage by alienated on Thursday June 23, 2016 @11:38AM (#11961823)
How is it incorrect - 'guys' (plural) is not gender specific, and refers to groups of people regardless of gender.

In addition to general usage anecdotes (of women using this word to address groups of women), I'm happy to provide dictionary citations if you'd like?

Re:Results of Rust Survey 2016 – early draft for internal usage by kbenson on Thursday June 23, 2016 @12:18PM (#11962173)
"Guys" is a fairly complex term[1]. Its common gender association changes when used plurally from male (when used singularly) to non-gendered. Like "man", when used in place of "humanity", I believe it's a holdover from a time when it was entirely acceptable to be dismissive of half the race. As such, it's probably appropriate to be at least a little sensitive to the topic, since it's not just a matter or speech norms, but a reference to past inequality.

1: http://english.stackexchange.com/questions/11816/is-guy-gend...

Re:Results of Rust Survey 2016 – early draft for internal usage by alienated on Thursday June 23, 2016 @01:03PM (#11962567)
> I believe it's a holdover from a time when it was entirely acceptable to be dismissive of half the race.

Ironically, when it was entirely acceptable to be dismissive of half the race, separate words were used - explicitly calling out a difference between groups. 'Guys' as a gender neutral term is a relatively recent phenomenon, and in many ways is an equalizing term.

> As such, it's probably appropriate to be at least a little sensitive to the topic

Alternatively you could argue that it's appropriate not to be over-sensitive to common, and innocent, language usage.

Re:Results of Rust Survey 2016 – early draft for internal usage by carols10cents on Thursday June 23, 2016 @01:20PM (#11962738)
Later in this thread, someone even uses it specifically to refer to only men:

> The reason I said hostile is that in most discussions on Hacker News and Reddit a lot of people argue that the only reason women are so under-represented in tech is that all the guys are very hostile to women. This survey goes against that. For some reason they refuse to believe that some things are more interesting to women than men and vice versa.

Re:Results of Rust Survey 2016 – early draft for internal usage by alienated on Thursday June 23, 2016 @01:37PM (#11962884)
I can happily find a reference (though not in this thread) to a woman using it to refer to a group of all women if you like...
Re:Results of Rust Survey 2016 – early draft for internal usage by carols10cents on Thursday June 23, 2016 @02:35PM (#11963352)
Since we both have anecdotes, anecdotes are clearly not going to "solve" this.
Re:Results of Rust Survey 2016 – early draft for internal usage by weberc2 on Thursday June 23, 2016 @09:22AM (#11960640)
> it is known to alienate people

I've not heard this before. Citation?