# To ECC or Not To ECC

**URL:** <https://discourse.codinghorror.com/t/to-ecc-or-not-to-ecc/3771>\
**Category:** blog\
**Created:** [November 19, 2015, 11:45pm UTC](https://discourse.codinghorror.com/t/to-ecc-or-not-to-ecc/3771 "2015-11-19T23:45:26Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![dudewhat](https://discourse.codinghorror.com/letter_avatar_proxy/v2/letter/d/c4cdca/32.png) [@dudewhat](https://discourse.codinghorror.com/u/dudewhat)\
**Post date:** [November 20, 2015, 4:05pm UTC](https://discourse.codinghorror.com/t/to-ecc-or-not-to-ecc/3771/18 "2015-11-20T16:05:54Z")

</div>

> Bad news though, ECC may not protect you from rowhammer:

Then I don’t want either. The fact that they’re selling memory with this problem is an example of everything that’s wrong with the computing industry. Give me memory that does its job, I don’t care how slow it is or what lack of it there is. I much rather work around memory limitations than check the entire codebase to see which parts are vulnerable to something like rowhammer.

---

_[View the full topic](https://discourse.codinghorror.com/t/to-ecc-or-not-to-ecc/3771)._