I mean I guess the summary could have been written in a more cunty way, but I don't see how. So high fives all round!

True. These infernal "computer" things would be going nowhere if it weren't for the clever marketing.

It's more sarcastic. Please try to keep up.

Before node.js it was literally impossible to use JS on a server. Thanks Node!!!1

Now we've got homeopaths and spiritualists involved, a cure for cancer must surely be just around the corner!!

Seriously?!

Why is Slashdot running a story about someone making a piece of simple (if awkward) equipment that has been used all over the world for decades?

" for a (highly negotiable) fee"

Oh, now I see. As you were.

But not very well, it would appear: http://www.ucdmc.ucdavis.edu/welcome/features/2010-2011/02/20110223_drug_dogs.html

Well...arguably. This is the exact same argument as Apache vs Nginx, where Apache spawns a child process per client, whereas Nginx has a limited number of worker processes that handle a queue of requests as they become free. Nginx definitely has an advantage in terms of RAM when servicing thousands of (truly) simultaneous requests.

While Postgresql does use the Apache model, there is middleware available (google 'pgpool' for an example) that amongst other things will queue requests so they can be serviced by a limited number of children. Of course this only matters if there are an awful lot of simultaneous queries (without the corresponding amount of server RAM).

However; your claim about threads per CPU is oversimplified, and especially wrong with a DB server where processes will most likely be IO bound. With 1 core, for example, there is nothing wrong with having 5 processes parsing and planning a query for a few microseconds, while the 6th is monopolising IO actually retrieving query results. Or the reverse - having 1 CPU-bound process occasionally being interrupted to service 5 IO bound processes, which would negligibly impact the CPU-bound query, while hugely improving latency on the IO bound queries.

Each client connected to the DB has its own child process - the shared memory is a buffer that is shared across postgresql child PIDs with the same parent. That's why the proposed patch would work using an anonymous shared memory segment - because the memory is only passed to children of the same process.

A polymath in a specific subject?

"didgital"? WTF am I typing?

I think claiming to have 192kHz DACs and then sticking a 20kHz filter in front of them would be...misleading. And looking at the datasheet it certainly suggests that the cutoff moves with sampling rate.

But whatever the cause, the point is that something like that should not pass without comment; that it has done indicates to me that the reviewer may not be particularly familiar with the subject.

I think what's most telling about their analysis is on the 96kHz plots. The Realtek consistently drops to nothing around 20kHz, and yet apparently that didn't mean anything to them other than "look how well these results fit with out hypothesis". Anyone who actually knew something about didgital audio would think "either I've set this up wrong or the drivers/hardware are bust, because this thing is blatantly stuck at 44.1kHz".

The only other thing to be gleaned from the graphs is that running at 96kHz is pointless because the supposedly better cards' performance FUCKING SUCKS past 20kHz.

Going by the information in that article, I have to say I agree with the justices. That's a fucked up system you guys have got:

The justices in London outlined a litany of concerns in their June 20 decision, noting offenders don't have to be mentally ill to be committed; their offenses don't have to be recent; and in some cases, they don't even have to have been convicted of a crime.

As of April 1, 641 people were in Minnesota's program...some who say it holds people indefinitely after their prison sentences. One 64-year-old man received a provisional discharge earlier this year...Only one other person was ever released from the program, and was soon taken back into custody on a violation.