> Another profitable industry besides mining could be setting up nursing homes on the moon, where wealthy elderly folks could live fuller lives due to the reduced gravity.
That's what SR Hadden did in Contact ;) as always, Carl Sagan is still teaching us to this day
> Not only are there enormous protections with the mis-use of one's credit card, but the 'password'/card number is randomly generated and not used elsewhere.
Not true. My mother got a free credit card that she never used and never even took out of her safe box, and a few weeks ago someone used that card to buy a Microsoft gift card. Luckily for her, she regularly checks the bank's statements.
I'm convinced there's a workaround to buy stuff using just the numbers, because that's how cards used to work a few decades ago.
Having a dollar budget would make the imbalance worse unless ideally they don't get away with moral hazard. The issue is usually having managers taking all the benefits and none of the risk, and that's bad.
Some industries require to be able to reproduce exact bit by bit data.
Anything that requires absolute bit certainty, for example digital signatures, encryption, or financial information, will require ECC.
If you don't care if your files eventually don't match a sha256 checksum, you'll be fine. for example source code, it doesn't matter because in the worst case, your code won't compile because variable names got flipped.
And even then, if you're using Git for source code control, you're already using hash signatures to detect data corruption, as well as a very large redundancy and replication. Git is, in a philosophical way, ECC by software.
> It depends on your workload.
> Some industries require to be able to reproduce exact bit by bit data.
> Anything that requires absolute bit certainty, for example digital signatures, encryption, or financial information, will require ECC.
Totally, and I get that. We've got people in this thread who are saying that non-ECC ram shouldn't be trusted [0], or that it should be standard [1]. I get the use cases, but why do I want that on my workstation.
> your code won't compile because variable names got flipped.
I have _never_ seen or even heard of this or anything vaguely resembling this happening. Are there any writeups of this anywhere at all?
ECC is expensive just because Intel had a monopoly over the server segment, and unilaterally forced desktop not to use ECC.
Otherwise people would use desktop computers as servers, and that would reduce profits.
At work, my workstation Desktop computer has ECC. The colleague's sitting next to me has on their screen sometimes kernel warnings of ECC errors.
And cases of bit flips happen every day, that's why some problems are solved by just restarting your computer or the software. I'd argue that many times we blame software bugs on pure hardware bit flips.
Argentinian economics at its best. Let's hope Egyptians come to their senses and realize that they can't get us dollars out of thin air and controls such as this will Only make it worse.
That's what SR Hadden did in Contact ;) as always, Carl Sagan is still teaching us to this day