I agree that for Virtualisation is great for managing machines (failover,migration,etc) but running a whole os in a vm just for browsing is ridiculous, it offers no real advantage to a chroot/jail while giving you more things that need to be kept up to date and so is infact *slightly* less secure
I'd already consider chroot just for browsing ridiculous. If you are paranoid, just run the browser under a different user ID.
But (most) humans have this innate condition where taking another life weighs on them somewhat - even most veterans and soldiers I know get twitchy about having to shoot at another person. A robot removes this and replaces it with cold logic.
I don't see a technical reason why a robot couldn't get that, too. It would be just a negative score for any killed human, which would enter the equation when making the decision.
Since there are four different bases, you need two bits to store a pair, which means you could get 4 bases into a byte without using any non-trivial compression method. But given that the genomes of different people are very similar, they should already save a lot of memory by storing just diffs to a "standard" genome (say, the sequence from the Humane Genome Project).
I guess he just saw that the link leads to some page at perl.org, didn't follow the link, wrongly assumed that it led to some Perl advocacy, and decided to put his Python link against it.
Well, that's an argument to have three size parameters: One for the size of the source array, one for the size of the destination array, and one for the amount to copy. After all, the amount to copy not just shouldn't exceed the destination array size, but also shouldn't exceed the source array size. So according to this argument, the perfect function would be
Indeed, throwing an exception is the worst thing you can do to such a low-level function (and yes, memcpy is about as low level as you can get).
High-level C++ code shouldn't use memcpy, simply because it's too low-level (it won't even work correctly if there's a non-trivial copy constructor). Use std::copy instead. For low level code, memcpy makes sense, but exceptions don't.
Why not just doing the same as the strnXXX functions, i.e. just stop copying at the end of the destination buffer? That is, just implement it as
3. While you are correct that the world will probably survive just fine as a whole, some of us are rather concerned about the amount of climate refuges we are going to see and in time the wars that will most likely follow.
Good point. Part of what killed the Roman empire was a slight climate change (the world getting colder), causing more people going southwards, where the Roman empire was "in the way".
We won't ever get a world without work, because there are many activities which you wouldn't do as hobby, e.g. I cannot imagine anyone doing canalisation cleaning as hobby.
That's fact, and what's fact is by definition fair, if the term has any meaning at all.
In some contries there's still (inofficial) slavery. That's a fact. So I should conclude it's fair? In some countries you can get arrested for saying something the government doesn't like. That's fact. Therefore it's fair?
Actually, according to your definition of "fair", there cannot be any unfairness in the world. Because whatever happens in the world is fact, therefore according to your definition it's fair.
That's a really bad analogy. The backup is not there in order to prevent hackers from breaking in, the backup is there in order to prevent loss if they break in, or if data gets lost for some other reason. That is, backups are not a security measure, they are a measure to limit damage.
Slashdot Mirror
Viola! The Worlds Worst Website
How does that web site relate to a Viola?
Probably because a cursor is about the simplest to control.
or let them go.
And in what country do you propose to deposit them?
The United States of America, of course.
I'd already consider chroot just for browsing ridiculous. If you are paranoid, just run the browser under a different user ID.
How did you get that through the junk character filter?
Not when it comes to security vulnerabilities.
Not when it comes to security vulnerabilities.
It's stable in respect to security vulnerabilities as well. No need to create new exploits just to keep your malware compatible.
But you can have killbots which kill killbots. Those don't need a limit (well, they probably shouldn't kill each other, but only the enemy robots).
On the positive side, there's no ethical problem about destroying a robot.
I don't see a technical reason why a robot couldn't get that, too. It would be just a negative score for any killed human, which would enter the equation when making the decision.
Since there are four different bases, you need two bits to store a pair, which means you could get 4 bases into a byte without using any non-trivial compression method.
But given that the genomes of different people are very similar, they should already save a lot of memory by storing just diffs to a "standard" genome (say, the sequence from the Humane Genome Project).
Isn't the plural of "volunteer", "volunteers"?
For the noun, yes. For the verb, no.
Java? Unlambda!
<marketingspeak>
</marketingspeak>
= never modifies the right-hand side of the equal sign, only the left hand side.
std::auto_ptr would like a word with you. This was one of the dumbest decisions the committee made.
Indeed. But the next version of the C++ standard will deprecate auto_ptr.
I guess he just saw that the link leads to some page at perl.org, didn't follow the link, wrongly assumed that it led to some Perl advocacy, and decided to put his Python link against it.
Well, that's an argument to have three size parameters: One for the size of the source array, one for the size of the destination array, and one for the amount to copy. After all, the amount to copy not just shouldn't exceed the destination array size, but also shouldn't exceed the source array size. So according to this argument, the perfect function would be
with an error if size exceeds either srcsize or destsize.
Indeed, throwing an exception is the worst thing you can do to such a low-level function (and yes, memcpy is about as low level as you can get).
High-level C++ code shouldn't use memcpy, simply because it's too low-level (it won't even work correctly if there's a non-trivial copy constructor). Use std::copy instead. For low level code, memcpy makes sense, but exceptions don't.
Why not just doing the same as the strnXXX functions, i.e. just stop copying at the end of the destination buffer? That is, just implement it as
Why does it matter if they control the drilling device with a CGI script?
Good point. Part of what killed the Roman empire was a slight climate change (the world getting colder), causing more people going southwards, where the Roman empire was "in the way".
The only question is in what group our species will be found.
Don't worry. It won't affect us before the CERN black holes have eaten the planet. :-)
There is no global warming. It's just the surface. The core temperature is unaffected.
1: Publish to PDF
3: Link to your homepage and paypal account
2: Post the torrent yourself
4: Profit!
No missing steps, yay!
But you do the third step before the second! :-)
We won't ever get a world without work, because there are many activities which you wouldn't do as hobby, e.g. I cannot imagine anyone doing canalisation cleaning as hobby.
In some contries there's still (inofficial) slavery. That's a fact. So I should conclude it's fair?
In some countries you can get arrested for saying something the government doesn't like. That's fact. Therefore it's fair?
Actually, according to your definition of "fair", there cannot be any unfairness in the world. Because whatever happens in the world is fact, therefore according to your definition it's fair.
That's a really bad analogy. The backup is not there in order to prevent hackers from breaking in, the backup is there in order to prevent loss if they break in, or if data gets lost for some other reason. That is, backups are not a security measure, they are a measure to limit damage.