Live data from Hacker News

Android’s 10 Millisecond Problem explained

superpowered.com

291–300 of 311 posts

Re: Android’s 10 Millisecond Problem explained

#291
post #171
post #152

Earlier quoted context omitted.

As someone who has actually done a good amount of soft-real-time audio programming, I can tell that you probably haven't. Everything you are saying about CPU speeds is made-up nonsense. Look into how these things are done on systems where folks actually care about latency (for example, commercial audio hardware, game consoles, etc).

I understand that people are downvoting this because it is just a negative comment, or something. But, I felt it was VERY important to call out information that is clearly false. Someone who doesn't know about audio programming might read the above post and think "hey that sounds plausible, I learned something today" when in fact they were deeply misled. Registering dissent is important and I tried not to be rude abo…

I thought it was a tad condescending. Instead of:

>As someone who has actually done a good amount of soft-real-time audio programming, I can tell that you probably haven't. Everything you are saying about CPU speeds is made-up nonsense.

You could have wrote:

>I've actually done a good amount of soft-real-time audio programming and everything you're saying about CPU speeds doesn't make sense.

I think it's good to call out what you see as misleading information but that may have been going a bit too far.

Re: Android’s 10 Millisecond Problem explained

#294

Earlier quoted context omitted.

Audiences have a natural tendency to slow down. They're mostly not musicians and I imagine their clapping as a response to the music (and the other clappers) rather than internalizing the music as a performer would.

If you start from a perfectly synchronized audience and assume they clap reactively, you'd expect them to delay each of their claps by ~1/2 speed of sound * width of the room. A good example for why on music you need a good rhythm (internal constant frequency driver) instead of acting reactively to perform well.

Yes, the audience will slow down regardless. Either the band slows down with them or they keep the same tempo and the clapping gets screwed up. It's frustrating as a performer trying to fight the audience and the only solution I know is to have the house levels sufficiently loud that the audience continually adjusts.

Re: Android’s 10 Millisecond Problem explained

#295
post #290

Earlier quoted context omitted.

You’re not wrong, but we’re arguing about different things, and I’m not sure how I can make myself clear. I think they didn’t mean to equate programming skill and masculinity. I also think they should be more sensitive in how they speak. I also think it’s dishonest to ignore the fact that one can be true without the other. Furthermore, “manly man” is a wacky satirical caricature of “real man”, a problematic stereotyp…

Actually, I think you've hit on something important: you're saying "manly man" is wacky and humorous, but "negro" is problematic. The only difference here and now is how it's no longer acceptable, at all, to play on race stereotypes, not like it was 50 years ago. Times change, and we can either keep up, or we can let ourselves becomes relics from an earlier era.

“Negro” was never humorous, as far as I know—it was just the name for a black person, or more accurately “a black”, through the lens of the culture at the time that dehumanised them by identifying them solely with their skin colour. However, I do see your point and I agree that it’s important to change with the times and adapt our language to the new, and hopefully more enlightened, cultural and historical context.

Re: Android’s 10 Millisecond Problem explained

#296
post #274

Earlier quoted context omitted.

I already do this exactly, in the case where it's one woman it would be humorous to use that statement and would lighten the mood. If someone is looking to be offended then they will find a reason no matter what is said or how it's said. Intent is the thing that should be judged, anything else is a foolish way to live and you will constantly find yourself offended.

I'm sure the old people I know who still refer to black folks as "negros" don't mean anything by it. I also bet the people who throw around "gay" as a generic pejorative aren't thinking of actual gay people when they use the word as an insult. That doesn't make either one acceptable here in the 2010s. Same with telling a woman that doing something "manly-man" style is doing it skillfully. And even if you know it's go…

I am black and would not be offended if someone referred to me as a negro, if they mean no offense, then I take no offense.

I've been referred to as African American, Afro American, colored, person of color, black, negro, etc. It makes no difference to me personally. Unless intended otherwise, it's just a point of reference.

Re: Android’s 10 Millisecond Problem explained

#297
post #274

Earlier quoted context omitted.

I'm sure the old people I know who still refer to black folks as "negros" don't mean anything by it. I also bet the people who throw around "gay" as a generic pejorative aren't thinking of actual gay people when they use the word as an insult. That doesn't make either one acceptable here in the 2010s. Same with telling a woman that doing something "manly-man" style is doing it skillfully. And even if you know it's go…

I am black and would not be offended if someone referred to me as a negro, if they mean no offense, then I take no offense. I've been referred to as African American, Afro American, colored, person of color, black, negro, etc. It makes no difference to me personally. Unless intended otherwise, it's just a point of reference.

Would you say that your personal experience is generalizable to many/most people of color?

If, say, someone from another company who's visited your offices for a day later refers to you as "that negro in product development," would it be typical that other people of color would take no offense at that use of language?

I'm curious about it. I don't have that lived-in experience, so all I can do to understand is ask and listen.

Re: Android’s 10 Millisecond Problem explained

#298
post #297

Earlier quoted context omitted.

I am black and would not be offended if someone referred to me as a negro, if they mean no offense, then I take no offense. I've been referred to as African American, Afro American, colored, person of color, black, negro, etc. It makes no difference to me personally. Unless intended otherwise, it's just a point of reference.

Would you say that your personal experience is generalizable to many/most people of color? If, say, someone from another company who's visited your offices for a day later refers to you as "that negro in product development," would it be typical that other people of color would take no offense at that use of language? I'm curious about it. I don't have that lived-in experience, so all I can do to understand is ask an…

I have customers from Latin America and negro in Spanish simply means black.

Why would I ruin my day and relationship with someone by taking offense to a word when there was no malice intended?

Re: Android’s 10 Millisecond Problem explained

#299
post #297

Earlier quoted context omitted.

Would you say that your personal experience is generalizable to many/most people of color? If, say, someone from another company who's visited your offices for a day later refers to you as "that negro in product development," would it be typical that other people of color would take no offense at that use of language? I'm curious about it. I don't have that lived-in experience, so all I can do to understand is ask an…

I have customers from Latin America and negro in Spanish simply means black. Why would I ruin my day and relationship with someone by taking offense to a word when there was no malice intended?

That may be, but I would appreciate if you could also lend me your insight into the questions I had asked.

Re: Android’s 10 Millisecond Problem explained

#300
post #244

Earlier quoted context omitted.

To call it "offensive" may be a bit strong (though I'd say it's offensive to those of us who enjoy good use of language ;) ), but exclusive? Sure. It links superior programming and masculinity. You're sitting in a conference room full of women who are developers, and you start saying, "So let's do some manly-man programming and get this done," what are these women supposed to think?

One would hope they were mature enough to understand an idiom, and not so delicate that they would need to be handled with kid gloves.

"not so delicate that they would need to be handled with kid gloves."

See... it's the little things like this. I am pretty sure that was not your intention, but please do know that turns of phrases like that hurt a little, and exclude a little.

To see what I mean, s/kid/jew/ or s/kid/white/ or some other category and see how it reads.

Post reply on HN