News for hackers. Stuff that matters.
Re:Math.random in V8 is broken by pcwalton on Friday November 20, 2015 @11:35PM (#10605629)
If your product is in a competitive environment and is being compared against others in benchmarks of random number generation, the answer is "as many as you can possibly generate".

This scenario corresponds to JavaScript engines of major Web browsers.

Re:Math.random in V8 is broken by tedunangst on Friday November 20, 2015 @11:43PM (#10605659)
In other words, bullshit breeds bullshit.
Re:Math.random in V8 is broken by pcwalton on Friday November 20, 2015 @11:49PM (#10605680)
I can't blame V8 engineers for not wanting to regress SunSpider. Sad or not—and, let me tell you, nobody who works on browsers likes this state of affairs when it comes to that benchmark—doing well on the popular benchmarks has to be an engineering goal in the environment browsers find themselves in.
Re:Math.random in V8 is broken by mmalone on Saturday November 21, 2015 @02:23AM (#10606054)
FWIW xorshift1024* would almost certainly be faster than MWC1616 and it has no systematic failures on BigCrush. The only downside is that it uses more memory, but I think we can afford it. If not xorshift64* is also faster than MWC1616 and miles ahead of it in quality.