We often get automated crash reports that, best we can tell, are just random bit flips (cosmic rays, hardware failure, rowhammer?
, ...). And I cant help but think, “How do computers run world like this?” 
-
-
-
Seriously—Chrome gets “invalid free” bugs from GWP-ASAN with surprising regularity, which happen apparently due to bit flips in the pointer being freed. It’s crazy.
- 2 more replies
New conversation -
-
-
You'd think memory safety would go without saying in any sort of "high assurance" application, but it is surprisingly still controversial
-
I recently had someone explain to me that memory safety was 'table stakes'. Oh sweet summer child...
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
From one of the links in that thread: https://en.wikipedia.org/wiki/Go_(programming_language)#Lack_of_race_condition_safety … " Instead of language support, safe concurrent programming thus relies on conventions;...
-
... for example, Chisnall recommends an idiom called "aliases xor mutable", meaning that passing a mutable value (or pointer) over a channel signals a transfer of ownership over the value to its receiver." If only there was a way to design a language to handle that automatically
- 1 more reply
New conversation -
-
-
This cannot be overstated enough and will probably be ignored for years to come.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.