News for hackers. Stuff that matters.
Re:Android’s 10 Millisecond Problem explained by kabdib on Thursday April 16, 2015 @11:04AM (#9388398)
I'd heard over the years that working with isochronous systems was difficult. I'd done a number of real-time systems before, and written OS schedulers and NTP-like systems and so forth. A little audio work should be a walk in the park, right? A little manly-man programming from the wrist and we move on to real problems. So I walked into an audio project thinking that "Oh, this latency and synchronization stuff, how bad could it really be?"

Bad.

Nailing down buffer-bloat and sources of latency and jitter in an isochronous system took several months, the last few weeks of which were 80-100 hour weeks just before ship. Several times we thought we'd fixed the issues, only to find that our tests had been inadequate, or that some new component broke what we had built.

I remember nearly being in tears when I finally realized what the clock root of the audio system actually was, and that it wasn't what people had been using. From there everything fell into place.

Don't pull the number of buffers you have out of thin air ("Oh, six is enough, maybe twelve, don't want to run out in my layer of the system, after all...") Don't assume your local underflow or overflow recovery strategy actually works in the whole system. Don't assume your underlying "real time" hypervisor won't screw you by halting the whole god damned system for 20ms while it mucks around with TLBs and physical pages and then resumes you saying, "Have fun putting all the pieces of your pipeline back together, toodle-oo!" Put debug taps and light-weight logging everywhere and attach them to tests. And know what your clock root is, or you will be sunk without a trace.

Isoch is hard.

Re:Android’s 10 Millisecond Problem explained by weaksauce on Thursday April 16, 2015 @01:53PM (#9389581)
A real postmortem of this would be a fascinating read.
Re:Android’s 10 Millisecond Problem explained by kabdib on Thursday April 16, 2015 @02:28PM (#9389858)
Well, if something bad happens I might have to work there again, so . . . not for a few years, probably :-)
Re:Android’s 10 Millisecond Problem explained by walterbell on Thursday April 16, 2015 @03:43PM (#9390329)
>when I finally realized what the clock root of the audio system actually was

How did you finally figure this out -- any recommended references?

Re:Android’s 10 Millisecond Problem explained by cbd1984 on Saturday April 18, 2015 @09:37AM (#9399404)
Flagged for sexism.
Re:Android’s 10 Millisecond Problem explained by cbd1984 on Friday April 17, 2015 @04:15AM (#9392859)
None of this is correct.
Re:Android’s 10 Millisecond Problem explained by cbd1984 on Saturday April 18, 2015 @09:35AM (#9399398)
Down votes don't make me wrong.
Re:Android’s 10 Millisecond Problem explained by gone35 on Thursday April 16, 2015 @07:04PM (#9391256)
"A little manly-man programming from the wrist and we move on to real problems."

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/man/jew/ or s/man/white/ or some other category and see how it reads.

Re:Android’s 10 Millisecond Problem explained by kabdib on Thursday April 16, 2015 @11:10PM (#9392068)
Well, if I wanted to offend, I would have. It is frankly no challenge to deliberately say something un-PC and widely offensive. It is also apparently little more challenging to utter something more subtle and more narrowly offensive.

I look at "manly man" depictions of, well, manly men (for instance, watch Kevin Kline's performance in A Fish Called Wanda) as parody. Monty Python did it. Mark Twain probably did it. Do they offend people? Sure. Do people not get the joke? Oh yeah. Did that stop the artists in question? Not really. Am I comparing myself to great artists? I'm not worthy, but I study at the feet of masters.

So, in my writing (and I've done a bit of it; look at my profile and my blog) I tend not to give a flying unmentionable about who I piss off. Now, HN is different because it's not my ball game here, but hey, if everyone wrote so as not to offend then the world would be a dull place. I've opposed what I believe is the actual evil -- Political Correctness -- for decades, and I'm not going to stop now.

I like to take language out and give it a violent shake. Have fun with it, see what it can do. I'm not going to change the world by substituting something benign and utterly unoffensive for "manly-man," so fuck it. That's what down-votes are for. I'm not even sure what I'd put there instead, quite frankly. Your suggestions don't preserve the meaning at all. Kevin Kline would be sad.

I regret that you were offended.

Now, can we Godwin this stupid thread and get it over with? Someone toss in the grenade, okay? in 10, 9, 8 . . .

Re:Android’s 10 Millisecond Problem explained by Frondo on Friday April 17, 2015 @03:35AM (#9392719)
"So, in my writing (and I've done a bit of it; look at my profile and my blog) I tend not to give a flying unmentionable about who I piss off."

Then I'm sure you're also OK with an ever-shrinking subset of the world being willing to put up with that tone.

It all works out, I suppose.

Re:Android’s 10 Millisecond Problem explained by cbd1984 on Friday April 17, 2015 @04:14AM (#9392850)
So you like to be an asshole and impede communications because you don't have anything of value to add, and you get offended when someone calls you on it?
Re:Android’s 10 Millisecond Problem explained by staunch on Thursday April 16, 2015 @11:18PM (#9392087)
BOOM
Re:Android’s 10 Millisecond Problem explained by yareally on Friday April 17, 2015 @12:11AM (#9392223)
I enjoyed the insights in your first comment and looked forward to reading this thread for obscure tidbits on audio latency on Android. However, instead of getting replies on your experience, we get a huge meta thread that contributes nothing to the original topic.

Sadly, some users have to disrupt a thread, no matter how inane or off-topic it might be :(. Sometimes it gets to the point I don't even want to read or contribute to the discussions on HN anymore and add the site to my hosts list so I won't be tempted to read it out of habit. Eventually I come back, but the times in between get longer.

After skimming the comment history of the person you're replying to, I'd just ignore them, because they have a history of doing this. If HN had an ignore list, they would surely be on mine. Won't be the first or last time they disrupt (troll) a thread.

Re:Android’s 10 Millisecond Problem explained by shaftoe on Thursday April 16, 2015 @08:27PM (#9391623)
I don't get it.

I read his comment as self-deprecating humor. If he had used white, jew, or whatever else may apply, it would still be self-deprecating humor, which is generally non-offensive for the simple reason it applies to the self.

Re:Android’s 10 Millisecond Problem explained by corndoge on Thursday April 16, 2015 @11:02PM (#9392049)
So, if cultural-linguistic idioms make use of a specific gender, they shouldn't be used because someone might get offended? At some point you have to assume that the other party is mature enough to understand and tolerate speech that isn't exactly tailored to their gender or sexual preference or race or what have you. I'm not going to cut out all the parts of my vocabulary that aren't perfectly 'equal' in the eyes of another.
Re:Android’s 10 Millisecond Problem explained by AaronIG on Thursday April 16, 2015 @07:50PM (#9391471)
The phrase he used has a fairly well understood meaning, so of course the substitution would read differently. It would be an entirely new phrase. Different words/phrases have different connotations.
Re:Android’s 10 Millisecond Problem explained by general_failure on Thursday April 16, 2015 @08:36PM (#9391651)
This comment is terrifying. You cannot say anything without being called out with this sort of terrible attitude.
Re:Android’s 10 Millisecond Problem explained by Frondo on Thursday April 16, 2015 @10:28PM (#9391965)
Of course you can. Language is intensely rich, there's such a tiny subset of stuff that we're now starting to recognize rubs people the wrong way/excludes people/makes us sound like cavemen.

I don't at all get what benefit there is to being able to say "manly-man programming," either from a communication or a social standpoint.

I don't get what's lost when we replace "manly-man programming" with anything less stupid and awful.

Re:Android’s 10 Millisecond Problem explained by general_failure on Friday April 17, 2015 @02:02AM (#9392461)
What's gained is language flair and color. You may not see it but I do.

This is like any other literature. Don't force the world into newspeak.

Re:Android’s 10 Millisecond Problem explained by bjt on Thursday April 16, 2015 @11:34PM (#9392129)
s/cavemen/cavepeople/
Re:Android’s 10 Millisecond Problem explained by general_failure on Friday April 17, 2015 @02:05AM (#9392469)
We should apply parent's logic here :)
Re:Android’s 10 Millisecond Problem explained by engi_nerd on Thursday April 16, 2015 @07:45PM (#9391445)
I did the substitution in my head and the statement sounds silly. Just like "manly-man" sounds silly.

Is this genuinely offensive and exclusive though?

Re:Android’s 10 Millisecond Problem explained by Frondo on Thursday April 16, 2015 @10:32PM (#9391982)
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?

Re:Android’s 10 Millisecond Problem explained by joenathan on Thursday April 16, 2015 @11:09PM (#9392064)
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.
Re:Android’s 10 Millisecond Problem explained by Frondo on Friday April 17, 2015 @03:39AM (#9392730)
Really?

So if your dev team consisted of a mix of men and women (not even counting if anyone identified as neither or somewhere in between), you'd still say "Let's put in some manly-man programming time" to them?

What if your dev team consisted of just one employee, a woman? Would you still tell her to put in her manly-man programming time? I'm having trouble seeing it. "Jane, it's crunch time. Can you man up and put in some manly-man programming time this weekend?"

Re:Android’s 10 Millisecond Problem explained by joenathan on Friday April 17, 2015 @03:57AM (#9392788)
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.

Re:Android’s 10 Millisecond Problem explained by Frondo on Friday April 17, 2015 @04:07AM (#9392828)
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 going to be taken as humorous, let me give you a hint: it's not very funny. It's just not very good as humor. There is much better material out there if you're going for a joke.

Re:Android’s 10 Millisecond Problem explained by joenathan on Friday April 17, 2015 @04:29PM (#9397014)
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 by Frondo on Friday April 17, 2015 @06:21PM (#9397509)
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 by joenathan on Friday April 17, 2015 @08:45PM (#9397933)
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 by Frondo on Friday April 17, 2015 @09:08PM (#9397978)
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 by Snesker on Friday April 17, 2015 @11:29PM (#9398215)
"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.

Re:Android’s 10 Millisecond Problem explained by smadge on Thursday April 16, 2015 @09:06PM (#9391735)
"phrases like that hurt a little, and exclude a little."

I agree with you on that part but your substitution doesn't make much sense.

The original comment links programming competency to masculinity, which is a problem. It's as simple as that.

Re:Android’s 10 Millisecond Problem explained by Snesker on Friday April 17, 2015 @11:33PM (#9398222)
Why is that a problem?
Re:Android’s 10 Millisecond Problem explained by rcr on Thursday April 16, 2015 @07:49PM (#9391465)
You can't really be serious.
Re:Android’s 10 Millisecond Problem explained by Frondo on Thursday April 16, 2015 @10:29PM (#9391971)
Sure he is. I for one look forward to when we drop these asinine phrases like "manly-man" from casual conversation and start speaking with a better, broader, more meaningful, and richer kind of vocabulary.
Re:Android’s 10 Millisecond Problem explained by ra1n85 on Thursday April 16, 2015 @10:36PM (#9391994)
I for one look forward to when language can be used in a way that the original author sees fit and without having to pander to every gentle sensitivity or taste.
Re:Android’s 10 Millisecond Problem explained by Frondo on Thursday April 16, 2015 @10:52PM (#9392025)
I don't know how the original author intended it, except that they seem to equate programming ability with masculinity.

If that's what they meant, that's a pretty retrograde attitude.

If that isn't what they meant, maybe it's time to update their vocabulary.

Re:Android’s 10 Millisecond Problem explained by evincarofautumn on Friday April 17, 2015 @03:28AM (#9392697)
We should be considerate in how we listen as well as how we speak. It does no good to speak insensitively, nor to listen oversensitively. Communication is a two-way street.

When I feel offended, I treat it as an opportunity to learn about a different viewpoint. Sometimes it makes me change my mind. It always gives me a better understanding of people.

Re:Android’s 10 Millisecond Problem explained by Frondo on Friday April 17, 2015 @04:10AM (#9392837)
The thing is, you've got a woman right here telling you, "this is exclusionary and seems stupid on the face of it." We don't even have to guess at how it's taken by someone who doesn't fit into its built-in description; they're telling us in plain language.

The different viewpoint, I guess, is that the original author has some outdated views on gender competence.

I've seen lots of comments saying "oh but it adds flair to language," and that's a reeeeeally weak defense. There is much better language available; that stuff just sounds stupid at best and retrograde at worst.

Re:Android’s 10 Millisecond Problem explained by evincarofautumn on Friday April 17, 2015 @09:13AM (#9394046)
I agree that the comment was insensitive. I never said otherwise. I was pointing out that you missed a case: it is entirely possible “that is not what they meant and they do not need to update their vocabulary”.
Re:Android’s 10 Millisecond Problem explained by Frondo on Friday April 17, 2015 @11:29AM (#9394900)
Of course it's possible they didn't mean to equate programming skill with masculinity. That doesn't mean that they don't need to update their vocabulary--just like those those elderly people I know who still use words like "negros" to refer to black folks.

Sometimes, the world changes, and it's up to us to keep up with the times.

(It's funny, I bet you anything if the original author had said "this negro gentleman at my workplace...", no one would be defending his retrograde use of language.)

Re:Android’s 10 Millisecond Problem explained by evincarofautumn on Friday April 17, 2015 @12:19PM (#9395315)
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 stereotype. “Negro” is just a problematic stereotype. I think we should find a better comparison, but one doesn’t come to mind.

Re:Android’s 10 Millisecond Problem explained by Frondo on Friday April 17, 2015 @01:32PM (#9395838)
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.

Re:Android’s 10 Millisecond Problem explained by evincarofautumn on Friday April 17, 2015 @03:25PM (#9396613)
“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 by Snesker on Friday April 17, 2015 @11:40PM (#9398232)
1. A woman saying something is exclusionary does not make it exclusionary on the basis that it's a woman who said it.

2.>original author has some outdated views on gender competence This is libel. This is not at all a conclusion that can be drawn from that user's posts. It's an unfair presumption and you're wrong to go around stating your opinions of others as facts.

Re:Android’s 10 Millisecond Problem explained by Frondo on Saturday April 18, 2015 @02:00PM (#9400382)
On point 1: if a woman says she feels excluded, then it's exclusionary. It's not up to you to decide how she feels or tell her how she should feel.

On point 2: I can't even dignify that "libel" remark with a response.

Re:Android’s 10 Millisecond Problem explained by DanBC on Saturday April 18, 2015 @02:08PM (#9400413)
Snesker is a holocaust denying troll.

The fact that this comment https://news.ycombinator.com/item?id=9200905 is still live and wasn't heavily downvoted says something about the current HN audience.

Re:Android’s 10 Millisecond Problem explained by Frondo on Saturday April 18, 2015 @02:51PM (#9400575)
Wow.

Thanks for pointing that out.

Re:Android’s 10 Millisecond Problem explained by Snesker on Monday April 20, 2015 @09:34PM (#9411832)
What part of my comment do you object to? Challenging the official story of the alleged holocaust DOES cost you your freedom in Germany, and also to a lesser extent in Canada. Do you think it should be a crime to disagree with the government? With Jews? With the 'general consensus'?

Furthermore, my remark doesn't prove in the least that I'm a troll or a holocaust denier. Use your logic. The fact that your comment is still live and wasn't heavily downvoted says something about the current HN audience.

Re:Android’s 10 Millisecond Problem explained by Snesker on Monday April 20, 2015 @09:30PM (#9411819)
Someone feeling excluded does not make something exclusionary. It's not up to you to decide someone's opinion is objective fact [i]simply because they're a woman, I might add[/i].
Re:Android’s 10 Millisecond Problem explained by gone35 on Friday April 17, 2015 @02:56AM (#9392604)
Sure he is.

Indeed. I'm glad at least one person got my point.

(A minor nitpick, tho: for the record I happen to have been born with two X chromosomes. Good guess though; especially on HN threads like these.)

Re:Android’s 10 Millisecond Problem explained by Frondo on Friday April 17, 2015 @03:36AM (#9392722)
Sorry! My bad, thanks for pointing out my assumption.