The supplier who gave them bad or subgrade steel should be, they're about to get reamed...

Heard on NPR this morning that they think it's an inside job, and has all the hallmarks of it being so.

Apparently someone got tired of the all unethical behavior. Something about an account being free to create, but $20 to delete (and then not really being removed, or something like that)

Oh. To answer your question - I've recorded at 96khz and played it back at 1/4 speed, and I don't recall seeing a dead zone on the resulting audible spectrum. So I couldn't say anything about 48khz and beyond, and I'll also caution I was hardly being scientific about it.

If I had anything that could reliably produce a sweep up there, I'd work on creating a graph for you. Sadly, I don't :|

Not bad for a cheap recorder, though. Even the battery life is nice. The -only- problem I have with it is the chassis is 'noisy' - I have a bit of paper towel wedged between the battery and the battery access panel, to keep it from rattling. If you're not handling it actively, it's quiet.

My $100 recorder picks up bird songs well beyond 20kHz. Doesn't seem to be aliasing either, as the pitch changes move harmonically and in the same direction as the stuff lower down that we can hear.

Maybe some are near water, another one is near high-grade ore, there are stations to service travelers between them, another one is in a better launch point to orbit, etc.

I'm not sure how parent got moderated Informative. Reddit does a pretty good job of not allowing offensive subs to pollute non-offensive ones. If you log on with the default set of subs, it's mostly non-offensive stuff with NSFW tags working pretty well to prevent you from following porn links and stuff. Yes, people talk about and/or link to offensive ones; but the offensive content itself is not in the stock subs. If you follow those links, you can find yourself in some truly bizarre and/or offensive places; but it's not in your face day-to-day unless you *choose* to go there.

We already solve it like programmers--we do it according to what the suits say, regardless of how stupid it is because... money.

The good programmers (would-be leaders) get disgusted and quit.

What we need is disruptive technology, from a different bunch of suits. This has nothing to do with how good the programmers are, except that if it's a good bunch of suits they'll attract a good bunch of programmers.

I'd say she's a lot more likely to get money from Uber than from non-existent multi-national cab companies.

Apparently, she didn't get enough. Let's see if she says anything about the "gig economy" a few months from now, and cross-reference that with the updated list of donors.

Snoop Dog's 'All my Bitches,' in C

SEGFAULT.
NPR announcer: We don't know much about Snoop, but apparently he was a pointer who liked to run free.

No money was lost, no value was lost

CARTOON: Man wearing a barrel running up to shack. Thin woman feeding scrawny baby from a can. CAPTION: Honey, great news! A guy on the Internet told me no value was lost!

Don't forget... They didn't build the A-10 and decide to put the GAU-8 in it - they took the GAU-8 and gave it wings. It's hard to beat that kind of focused purpose.

Rust can't be used to build a kernel because you can't handle OOM reliably.

From context I'm getting that's Out Of Memory. I don't know much about Rust; but what you're describing sounds more like a problem with the current implementation rather than the language itself... unless the developers painted themselves into a corner by specifying that allocation failure must panic and can't return something like a NULL.

Me, personally? I wouldn't want to do anything you describe. I'm wagering Linus doesn't either. The question was if he was *interested* in these new languages. Laying that aside now, what you're describing might be easier with Clang. That leads (heheh) to another question, and a quick googling seems to indicate that the kernel can't be built with Clang yet...

This is close enough to the question I had in mind that I've decided to comment on this thread instead. My question would have been phrased as: Do you ever see yourself wanting to do kernel programming in something other than C and assembly?

Particularly I'm wondering if he has any interest in Rust or Go, since they are actually targeting themselves at lower levels. I doubt he'd want to put Haskell in the kernel; whereas he might have different opinions about it outside that domain. Of course hopefully he'll answer so we won't have to speculate.