Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why React Native Is Different

jlongster.com

Post reply on HN
Print view View original

61–69 of 69 posts

Re: Why React Native Is Different

#61

Post by Cushman »

nkozyra wrote: post #59
Cushman wrote: post #55

Earlier quoted context omitted.

> I don't mean to be curt I'll repay the same courtesy: Your argument is predicted and refuted by your sibling thread of twenty minutes ago. https://news.ycombinator.com/item?id=9501084 Microaggression is a term of jargon, as Google would have happily informed you. Its root word, not its synonym, is "aggression". Microaggressions are by definition not intended to hurt, or they would be, you know, aggressions. That's…

To be fair, I responded within that sibling, even before this response. I will reiterate, though, that it's impossible to capture or represent the feelings of a large group with a one-sized-fits-all rule. Whether I accept them or reject them depends exclusively on the reality of the situation and audience.

I apologize! I did in fact not mean to be curt, and I felt so bad about that that I edited in a more complete response that you will hopefully prefer :)

Great, and now you've edited so that I look like the crazy one...

Re: Why React Native Is Different

#62

Post by natural219 »

logicallee wrote: post #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, th…

I hate to pile on, but I also find this incredibly hard to read. The problem is that the precision with scrolling one "slide" down is very hard to get the same every time. Clicking a right arrow guarantees one click, one slide, whereas with this UX I'm constantly scrolling, then reading, then scrolling, then reading, and it's enough to make me not want to read the content.

I'm normally not a UX pedant, either.

Re: Why React Native Is Different

#63

Post by __david__ »

egh wrote: post #31
arcatek wrote: 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?

No. If I address a mixed gender group, and I ask that "all the guys" raise their hand, everybody will know that I mean men only.

Well, duh, that's because you used it in a non-gender-neutral way. If you said, "hey you guys, raise your hands", then that is way more gender neutral. Like all of language, differences in meanings can be subtle. They can also depend on where you are from.

Re: Why React Native Is Different

#64

Post by bmelton »

HAAAAMMMM wrote: post #44
Cushman wrote: post #33

Earlier quoted context omitted.

You're literally describing what microaggressions are: Small interactions, any one of which is harmless and without ill intent, which accumulate over the course of the day, week, or lifetime as an atmosphere of pervasive discrimination which is completely invisible to those responsible for creating it. Microaggressions are insidious precisely because they're so innocuous; they let well-intentioned people participate…

> You're a well-meaning person, and you want to avoid causing unnecessary harm with your words. I don't like the weaselly binary assumption here. You are implying "You are either a well-meaning person or you are not." That's an unbelievably narrow (and, honestly, childish) view of human interactivity. It also implies that you alone hold a monopoly on how "well-meaning" is defined and that it is your sacred duty to im…

'You are implying "You are either a well-meaning person or you are not."'

I think that's appropriate, actually. That you've defined well-meaning to encapsulate more people than it does is probably the core of the disagreement, but I think it's fair to say that most people are well-meaning, but not all people are.

Comparing and contrasting "almost everybody" to "Ann Coulter", and I think it's easy to draw such a distinction. Most people are simply trying to communicate without deliberately pissing everybody off, while Ann Coulter gets pretty decent play out of pissing people off for the hell of it.

That said, your point on "well-meaning" being an arbitrary distinction holds, though I would assert that if more people assumed good faith until proven otherwise, we wouldn't find ourselves being offended by every little thing.

Re: Why React Native Is Different

#65

Post by kaonashi »

bmelton wrote: post #48
DanaDanger wrote: post #28

Earlier quoted context omitted.

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

Folks is a classist, and refers to commoners, which might be considered offensive to those in the audience with aspirations, as well as to those in the audience in the upper class. Note, that was slightly tongue in cheek, but this is apparently what we do with words today... find some way in which they could be considered offensive, and then immediately begin to take offense at them. While I understand that there are…

Punching up vs. punching down.

Re: Why React Native Is Different

#66

Post by afarrell »

Cushman wrote: post #52
afarrell wrote: post #46

Earlier quoted context omitted.

yea. Agression implies intent. Microagression does not. Which can actually be kinda confusing to folks not familiar with it, but this is true of many sets of jargon, not just Social Justice.

It's definitely a crappy word out of context, and the defensiveness is probably to be expected. Who are you calling aggressive!... On the other hand, it's routinely frustrating when especially technical communities, full to bursting with misappropriations of common terms, seem especially unable to see past the letters in a word to its meaning in context. Maybe we just intrinsically don't believe that other areas of i…

One problem is that most fields accept that their jargon is in fact jargon that folks have to learn. Some chunk of SJ folks don't, which is dismaying because it ignores educational privilege.

Re: Why React Native Is Different

#67

Post by Cushman »

afarrell wrote: post #66
Cushman wrote: post #52

Earlier quoted context omitted.

It's definitely a crappy word out of context, and the defensiveness is probably to be expected. Who are you calling aggressive!... On the other hand, it's routinely frustrating when especially technical communities, full to bursting with misappropriations of common terms, seem especially unable to see past the letters in a word to its meaning in context. Maybe we just intrinsically don't believe that other areas of i…

One problem is that most fields accept that their jargon is in fact jargon that folks have to learn. Some chunk of SJ folks don't, which is dismaying because it ignores educational privilege.

That's a good point, though I don't think it's such an uncommon thing; think of the beginning programmer who has to be laboriously convinced that the first definition they learned for "type" or "function" is not the meaning of that word.

I'd speculate that true appreciation for jargon comes more from multidisciplinary studies than anything else, so in any field the most passionate, least experienced members are likely to make a mess of things-- and if there's one thing the activist community has in surplus it's members with a high passion:experience ratio.

Having acknowledged that issue, I'm still reluctant to excuse anyone in this case, simply because we're talking about a term that doesn't have any other meaning. If you see a word you've never heard before, and think "I can probably figure out what this refers to based on its sounds" with Google sitting right there, naah, the problem isn't the jargon.

Edit: Like, seriously, would this happen if the word was "microclimate" or "microevolution"? Yeah, on the YouTube comments, but not usually on HN.

Re: Why React Native Is Different

#68

Post by afarrell »

Cushman wrote: post #67
afarrell wrote: post #66

Earlier quoted context omitted.

One problem is that most fields accept that their jargon is in fact jargon that folks have to learn. Some chunk of SJ folks don't, which is dismaying because it ignores educational privilege.

That's a good point, though I don't think it's such an uncommon thing; think of the beginning programmer who has to be laboriously convinced that the first definition they learned for "type" or "function" is not the meaning of that word. I'd speculate that true appreciation for jargon comes more from multidisciplinary studies than anything else, so in any field the most passionate, least experienced members are likel…

That is a really good point about the uniqueness of the term.

Also, I had completely forgotten that "function" also means, like, cocktail parties.

Re: Why React Native Is Different

#69

Post by Cushman »

afarrell wrote: post #68
Cushman wrote: post #67

Earlier quoted context omitted.

That's a good point, though I don't think it's such an uncommon thing; think of the beginning programmer who has to be laboriously convinced that the first definition they learned for "type" or "function" is not the meaning of that word. I'd speculate that true appreciation for jargon comes more from multidisciplinary studies than anything else, so in any field the most passionate, least experienced members are likel…

That is a really good point about the uniqueness of the term. Also, I had completely forgotten that "function" also means, like, cocktail parties.

Heh, love it. "Can you call that function next door and find out if it's ever going to halt?"
Post reply on HN