News for hackers. Stuff that matters.
Re:Math.random in V8 is broken by mistercow on Friday November 20, 2015 @11:18PM (#10605576)
I would definitely argue against that given the perf that you can get out of CSPRNGs. AES/CTR could give you over 100 million random bytes per second back in 2009 (source: https://www.cryptopp.com/benchmarks.html).

How much faster do you need your RNG to be in any non-niche situation?

Re:Math.random in V8 is broken by Jach on Saturday November 21, 2015 @04:12AM (#10606263)
The niche situations aren't going to use the built-in rand() anyway because they can write their own or use someone else's that's faster. Even if they end up using the same algorithm (e.g. a Mersenne Twister) they can still often go faster.

Interestingly according to https://bocoup.com/weblog/random-numbers Firefox is just going to use its CSPRNG once the crypto api is ready. (Bug 322529 is still in NEW state, though.)

Re:Math.random in V8 is broken by iopq on Saturday November 21, 2015 @08:22AM (#10606729)
I need it faster because I need to generate random values for montecarlo trials. So I am using xorshift now instead of the default.