3 ms·
I'm not following his reason for writing this. In part 2 he says he doesn't care about the performance hit from a crypto library that implements a system TRNG,
by iheartpotatoes 8y ago
I'm not following his reason for writing this. In part 2 he says he doesn't care about the performance hit from a crypto library that implements a system TRNG, sooooo, use that?
https://developer.mozilla.org/en-US/docs/Web/API/Crypto/getRandomValues https://developer.mozilla.org/en-US/docs/Web/API/Crypto/getR...
Or even study the thread on entropy pool paranoia from the Stanford Javascript Crypto Library:
https://github.com/bitwiseshiftleft/sjcl/issues/77 https://github.com/bitwiseshiftleft/sjcl/issues/77
/scratches head at FAIC/
- detaro 8y agoWhy are you linking to Javascript docs under an article about why the default C# APIs for random are bad? And even if there's already replacement libraries, a discussion of how they can be better than the default is useful?
- ericlippert 8y agoThe reason for writing this is to gently introduce the general topic of improving how we represent stochastic workflows in mainstream programming languages. Entering that complex topic by exploring just how horrid even the most basic aspects of randomness are represented is an accessible and compelling entry point. This is part three of a very long series that will explore the connections between LINQ, probability distributions, and the difficulties of sampling from arbitrary distributions.