Live data from Hacker News

Why React Native Is Different

jlongster.com

21–30 of 69 posts

Re: Why React Native Is Different

#21
post #10

Earlier quoted context omitted.

Given the fluidity of language, I'd say it's common enough that it is now correct as a gender-neutral address, like "folks" or :shudder: "y'all."

Not really. It's still a microaggression in gender-sensitive contexts (such as women in tech)

If you think pronoun accuracy is a primary concern regarding women in tech, I'm going to guess you have never seen a woman in tech. They are far more concerned about memory leaks and pointer management.

Re: Why React Native Is Different

#22
post #2

> "To the women readers/watchers: I apologize for saying "guys" in a few places referring to groups of people" As a non-native speaker, isn't "guys" a correct term regardless of the gender?

It's regional and context-specific. On the U.S. coasts, "guys" is considered gender-neutral when used in an address (e.g. "you guys" or "guys, listen to this"). It seems like depending on region it might be the case that "guys" can be broader (e.g. "Facebook guys" being gender-neutral), although personally as someone who grew up in the Northeast that sounds non-idiomatic to me.

(Edit: here's a link to the Harvard Dialect Survey that shows regional variations in addressing groups of two or more people: http://www4.uwm.edu/FLL/linguistics/dialect/staticmaps/q_50....)

There's been some linguistic research that shows that men are more likely to interpret "guys" as neutral than women, although unfortunately I don't have a link.

Some people prefer not to use the "guys"-as-gender-neutral slang even on the coasts both because it sets male as default and because it can be misinterpreted by people from other parts of the U.S. and the world. Personally I've stopped using it unless I'm actually addressing a group of dudes.

Re: Why React Native Is Different

#23
After getting tired of scrolling (which reminded me of this http://joshworth.com/dev/pixelspace/pixelspace_solarsystem.h... where you scroll through vast distances to appreciate how far apart things in our solar system are) and noticing the huge headings separated by large vertical whitespace, I had an idea: since the headings are so huge, I could just zoom way out and see and read all the headings!

Unfortunately, the page outsmarted me and as I zoomed out, it somehow figured out I was doing this and increased the font size so it's the same size it was at 72 points when I was at 100% zoom.

Well, all right web designer. You "win". The amount of effort you put into defeating my efforts to read your content is astounding.

Re: Why React Native Is Different

#24
post #2

> "To the women readers/watchers: I apologize for saying "guys" in a few places referring to groups of people" As a non-native speaker, isn't "guys" a correct term regardless of the gender?

I have used "guy" in the past and now make a conscious effort to avoid it. There's no need to create an implicit bias when saying something like, "We'll need to recruit some Python guys to deal with this." Just use "people" instead. (Unless you're referring to the guys in the men's room.)

> There's no need to create an implicit bias when saying something like, "We'll need to recruit some Python guys to deal with this."

I might question whether the speaker or the listener would be the one creating the supposed bias in that case.

Re: Why React Native Is Different

#25

After getting tired of scrolling (which reminded me of this http://joshworth.com/dev/pixelspace/pixelspace_solarsystem.h... where you scroll through vast distances to appreciate how far apart things in our solar system are) and noticing the huge headings separated by large vertical whitespace, I had an idea: since the headings are so huge, I could just zoom way out and see and read all the headings! Unfortunately, th…

The amount of work is simple:

h1 { font-size: 5vw; }

The `vw` units are relative to the page width.

You would rather have to press the right arrow key 50 times? I find it to be a whole lot faster to scroll quickly through content rather than forcing me to click through every single damn slide.

EDIT: It is interesting that the vw/vh units don't take zoom into effect, I hadn't thought of that. Interesting.

Re: Why React Native Is Different

#26

After getting tired of scrolling (which reminded me of this http://joshworth.com/dev/pixelspace/pixelspace_solarsystem.h... where you scroll through vast distances to appreciate how far apart things in our solar system are) and noticing the huge headings separated by large vertical whitespace, I had an idea: since the headings are so huge, I could just zoom way out and see and read all the headings! Unfortunately, th…

It's not actually figuring anything out. The header is specified in vw units, which are relative to the size of the viewport.

Re: Why React Native Is Different

#27
post #24

Earlier quoted context omitted.

I have used "guy" in the past and now make a conscious effort to avoid it. There's no need to create an implicit bias when saying something like, "We'll need to recruit some Python guys to deal with this." Just use "people" instead. (Unless you're referring to the guys in the men's room.)

> There's no need to create an implicit bias when saying something like, "We'll need to recruit some Python guys to deal with this." I might question whether the speaker or the listener would be the one creating the supposed bias in that case.

As is usual with communication, the answer of "who creates the resulting effect" is "both the speaker and listener, not one or the other". Particularly, in this case, the speaker's contribution comes by choosing a term which has both a male-gender-specific and a gender-neutral sense rather than something unambiguously gender-neutral.

Re: Why React Native Is Different

#28
post #2

> "To the women readers/watchers: I apologize for saying "guys" in a few places referring to groups of people" As a non-native speaker, isn't "guys" a correct term regardless of the gender?

This is a matter of some controversy. There's pressure to shift away from using it in gender-neutral contexts, but there's certainly no broad agreement.

If you want to play it safe, use "folks."

Re: Why React Native Is Different

#29

After getting tired of scrolling (which reminded me of this http://joshworth.com/dev/pixelspace/pixelspace_solarsystem.h... where you scroll through vast distances to appreciate how far apart things in our solar system are) and noticing the huge headings separated by large vertical whitespace, I had an idea: since the headings are so huge, I could just zoom way out and see and read all the headings! Unfortunately, th…

The amount of work is simple: h1 { font-size: 5vw; } The `vw` units are relative to the page width. You would rather have to press the right arrow key 50 times? I find it to be a whole lot faster to scroll quickly through content rather than forcing me to click through every single damn slide. EDIT: It is interesting that the vw/vh units don't take zoom into effect, I hadn't thought of that. Interesting.

actually, yes. Compared to scrolling football fields to get to the next item, a one-push interaction would be better.

Re: Why React Native Is Different

#30
post #2

> "To the women readers/watchers: I apologize for saying "guys" in a few places referring to groups of people" As a non-native speaker, isn't "guys" a correct term regardless of the gender?

It's regional and context-specific. On the U.S. coasts, "guys" is considered gender-neutral when used in an address (e.g. "you guys" or "guys, listen to this"). It seems like depending on region it might be the case that "guys" can be broader (e.g. "Facebook guys" being gender-neutral), although personally as someone who grew up in the Northeast that sounds non-idiomatic to me. (Edit: here's a link to the Harvard Dia…

[deleted]
Post reply on HN