Apparently if you stop it in the middle you lose data
I stopped it in the middle by clicking cancel. It instantly stopped. I lost no data, and there was no 'reversal' procedure. Perhaps this is because I had enough free disk space that it didn't have to delete as it progressed, and could wait until the end.
Because it was instantaneous, I don't think that even an abnormal stopping would have cost me any data (though perhaps I'd have had to delete the file it had been constructing.) However, if as you say it deletes as it goes when space is tight, then I think under those circumstances it would be dangerous to use.
Obviously the file that it's writing could be corrupted, but the existing files that are only being read shouldn't be affected. And in fact, I doubt that it actually does, and I think the assertion that FileVault is causing data loss due to users resetting the computer is incorrect.
It's just the opposite for me. I can see dozens of other Macs that are on the same cable modem subnet. Just for snicks I've tried connecting to a few, but no one is using an easily guessed account and password.
For those who don't know who this guy is, he wrote some ground-breaking games way back when. Eastern Front for the Atari 800, Balance of Power for the early Macintosh, and others.
That little invention really reflects how stupid this guy is.
Calling Simonyi stupid, is, well, stupid. Or at the very least ignorant. He's brilliant. And he invented his notation while writing in C, a language not known for its abstraction.
Visual Basic made it possible for untrained people to write software, and Access made it possible for untrained people to write database applications, but neither of those applications has reduced or eliminated the need for people to create software.
Your argument is basically "it hasn't happened yet, so it isn't going to." Using that same argument, I could conclude that if I don't die the first time, then Russian roulette is safe.
That's also why ships leaving a planet would be right side up for the viewer, but upside down for the planet.
Maybe so, but Kasparov played a damn fine game.
Well, since they didn't give up when the first actual city was hit, then probably not. Also, they didn't exactly have a huge supply of bombs.
I stopped it in the middle by clicking cancel. It instantly stopped. I lost no data, and there was no 'reversal' procedure. Perhaps this is because I had enough free disk space that it didn't have to delete as it progressed, and could wait until the end.
Because it was instantaneous, I don't think that even an abnormal stopping would have cost me any data (though perhaps I'd have had to delete the file it had been constructing.) However, if as you say it deletes as it goes when space is tight, then I think under those circumstances it would be dangerous to use.
Obviously the file that it's writing could be corrupted, but the existing files that are only being read shouldn't be affected. And in fact, I doubt that it actually does, and I think the assertion that FileVault is causing data loss due to users resetting the computer is incorrect.
Why would you think that? That's just downright stupid.
So what happens if I have a power failure?
It's just the opposite for me. I can see dozens of other Macs that are on the same cable modem subnet. Just for snicks I've tried connecting to a few, but no one is using an easily guessed account and password.
I like yours better.
"(C) SCO", I believe.
I like it.
Eastern Front for the Atari 800, Balance of Power for the early Macintosh, and others.
He's also written extensively on game design.
Shouldn't that be finger?
This reply has no
Calling Simonyi stupid, is, well, stupid. Or at the very least ignorant. He's brilliant. And he invented his notation while writing in C, a language not known for its abstraction.
Your argument is basically "it hasn't happened yet, so it isn't going to." Using that same argument, I could conclude that if I don't die the first time, then Russian roulette is safe.
Not all projects start from a clean slate. This post explains a bit.
Man, that is one crappy sentence. Distrubing, even.
That -i586mmx is incorrect. -squirrelGoFaster.wheel is the proper modifier.
+187, Insightful
That's pretty funny.
How often do they actually decrease, no matter what the government is up to?
Why would you say "7-8"? If seven is not always enough, then it should be just 8. And if seven is enough, what do you need the 8 for?
If that's the case, then why haven't I given up any storage space? Is it deceiving me?
Nearly both.