Sure, if they're Houyhnhnms.
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
In case you're not feeling paranoid enough yet:
Reflections on Trusting Trust
I'm not sure you really understand how salting a password works.
There's never any point in "trivial" salt.
Salt is a public random value (randomly generated for each password), the same size as the hash. It's stored in plaintext alongside the hash.
To check the password, you hash <salt><password>. It's effectively impossible for <salt><password> to be in a table no matter what <password> is. It doesn't prevent brute-forcing the password in other ways of course.
I'm not sure what your deep-deep-dark secret password would enable.
Actually Mono Lake has been protected and its water level is currently going up.
Unless he needs some time to finish reading "the pet goat"
I think it should have been multiple times more massive then the sun.
But the current state of things is that we pay more for data than for voice.
I wish more cyclists were like that, too. It's really annoying, as a cyclist, to stop at a red light, to be passed (often on the right, and very close) by another, slower cyclist.
What's the difference actually? I'm not an expert in contract law.
Non-compete agreements are typically illegal in California.
100 pounds of enriched uranium is a lot.
Allow me to introduce these concepts:
while (source[i] != '\0')
dest[i] = source[i];
So one error in that code would be 1 defect per five lines or so.
Here's all the code you need, what a better programmer would write:
while (*dest++ = *src++);
Your "better code" is actually not equivalent (the first loop doesn't copy the nul terminator). Even if it was equivalent, I don't think I would necessarily call it "better". This particular piece happens to be fairly idiomatic and many would understand it, but cramming as much semantics in one line as possible is usually not a good idea. I agree that in general less code is better for equivalent behavior, but usually that means better factoring, not putting more code in one line.
> something that predated the definition of units in the metric
> system in physical units by almost 200 years.
That definition depends on gravity at the point of measure (I think. I'm not sure what's "a pendulum at 38 degrees"). How is it more a "defined in physical units" than 1/10,000,000 the distance from the equator to the North pole (original definition of the meter), of the mass of a given volume of water (original definition of the kilogram)?
Most NPC problems fall into this category.
Actually, by definition, *all* NP-complete problems fall into this category (unless P = NP)