|
|
|
|
|
by frankreyes
975 days ago
|
|
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. 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. |
|
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?
[0] https://news.ycombinator.com/item?id=37829796
[1] https://news.ycombinator.com/item?id=37828865