And why are you discussing crashes? Rowhammer is usually considered a security vulnerability, not a general reliability issue, right?
I'm confused by what you're trying to say.
The goal of a computer for the majority of users (aka, not us developers) is thereby to be as cheap as possible while being just stable enough to not fail so often as to be too annoying, while preferably being as fast as possible under highly constrained conditions to play games at high quality.
I’m sure many people would use RAM that’s cheaper and faster but row hammer vulnerable. Just as many people drive cars with engines that will break if driven at redline for long periods of time.
It’s not like row hammer is a realistic use case. No algorithm depends on row hammer access patterns. Just like people don’t buy cars to bounce off the rev limiter.
On the other hand, is not only row hammer attacks that cause bit flips, random bit flips happens, cosmic ray or decline of radioactive particles might cause one. And there is _no way_ to know if one happened on non ECC RAM (I know, ECC only reduces the probability of not noticing it, but it reduces that probability), and given that there is not way to respond.
If one random bit flip happens, best case nothing happens. If you are unlucky, maybe your system will crash. If you are really unlucky your data might end up corrupted and the OS might not even be able to detect it. Or maybe you were running a 100 hours calculation, and it might go wrong in the first minutes because of a bit flip and your simulation is ruined.
Floating point operations is about precision, witch can be studied and decided based on the needs of the application, bit flips are about data corruption.
Edit: downvotes? Really?