No, "I couldn't care less" means "it's not possible to care even less than I already do, even if I wanted to". It means I care the least possible amount. I have reached the bottom.

"I could care less" (but I don't, meaning that I do care a certain amount) means that there is still a margin between the amount I care and the least possible amount of care. I haven't reached the bottom. Nothing is said about the size of that margin, so this statement really doesn't say anything.

It is a completely relevant question. If a quarter of the population never have used the web, but half of the population has Internet access, it follows that either half those with Internet access have never used it, or that the sentence is formulated so poorly that misunderstandings are bound to ensue.

No, it means that half those without Internet access have never used it.

I speak Dutch too (I'm Flemish). I'm often inclined to write "an USB stick" like you do, because I often think of the Dutch pronunciation of USB which indeed starts with a vowel.

But what matters when writing English is, of course, the English pronunciation, not the Dutch one. In English it is pronounced like joe es bie, so the first sound is not a vowel, so it should be "a USB stick".

All the wireless mouses I've used worked perfectly, for about 98% of the time (not counting empty batteries). 2% of the time they would fail. 2% of the time doesn't sound like much, but it's very frustrating.

The wired mouses I use now work perfectly 100% of the time. The cable is not really a problem since I connect it to a USB hub on the desk, or a USB hub in the keyboard (Why is it so hard to find a keyboards with a USB hub? It's damn practical). I never need to charge the batteries. Much better than wireless, in my view.

The size of the flash unit was given in gigabits, not gigabytes.

32 * 512 Gb = 16384 Gb = 2048 GB.

Deb ee Ann

It's easy to remember, once you know where it comes from. To cite Wikipedia:

The original "Debian Linux" distribution was released in August 1993 by developer Ian Murdock, and was named as a combination of his own given name and the given name of his girlfriend at the time, Debra Lynn.

I stand corrected. It surprises me that I never heard of it before.

Not to mention the tidal forces make the Earth's surface flex about 1ft (as evidenced by my GPS) per day.

I find that very hard to believe. If there is any flexing of the Earth's surface, I don't believe it to be more than a fraction of a millimeter (unless shown convincing evidence to the contrary).

GPS is not a good tool to accurately measure heights: GPS isn't very accurate vertically, and even horizontally the errors are normally more than a few feet.

Look at nuclear weapons - despite quite a few countries having them at this point, only a few have been used.

FTFY.

The world is afraid some rogue state like North Korea might launch a nuclear attack, but so far only one state has shown it is willing to go the whole way and actually do it. It's not North Korea, China, Iran, Pakistan, ..., but much closer to home (for most Slashdot readers). I'll leave it to others to comment on what that might or might not tell you about the sanity of that state.

I'd rather live at the mercy of the bacteria, which is very natural and is what we've been doing since the very beginning, than live at the mercy of pharmaceutical companies.

The judges ended up accepting it due to the ambiguity of the question.

Don't you mean the ambiguity of the answer?

God wins!

Is that a clever pun on Godwins' law, or is it just a very fortunate coincidence?

As I understand it, the problem is not with the database but with the client library. That library is dual-licensed GPL and something proprietary. There's no problem if you use that library in a GPL application, but otherwise you have to use the proprietary-licensed version. Which costs money.

If I'm right, you could work around the problem by writing your own client library (I have no idea how difficult that would be) and using that instead of theirs.

As I understand it, he proposes a system where each pixel (meaning in the image format, not on the physical display) can be subdivided in two areas, with different possible shapes (two rectangles on top of each other, two rectangles next to each other, two triangles) and different sizes of the two shapes. The best way to subdivide is decided for each pixel, in a way that maximizes the contrast between the two areas.

Or something like that; the text doesn't make it very clear.

Filenames with spaces in them are not broken; code that fails to deal with them is broken.

There are no good reasons not to use spaces in filenames, other than code that doesn't handle it because of wrong assumptions. That is a failure of the code, not of the user wanting to use meaningful filenames. The OS exists to give the user a nice interface, within reasonable limits; not to impose arbitrary limits.

It's true that Unix command line and script environment doesn't handle spaces very well. I think that's sad.