News for hackers. Stuff that matters.
Re:Specific Problems with Other RNGs by tptacek on Wednesday November 11, 2015 @04:04PM (#10549273)
So basically the only normal engineering reason to use PCG is if you need deterministic insecure random numbers: in other words, for simulations and testing code.

It is hard to imagine another scenario in which using an insecure RNG is good engineering. Secure RNGs are somewhat costlier than fast insecure RNGs, but it is very hard to predict which incidental random numbers won't ever need to be secure.

(I would generally take anything 'pbsd says about RNGs to the bank.)

Re:Specific Problems with Other RNGs by Veedrac on Wednesday November 11, 2015 @04:20PM (#10549369)
If you're fine with a cryptographic RNG, then definitely. I'd even agree that cryptographic RNGs should be default. Rust made the right choice here.

But look at C++'s new RNG library. Go's random library. People don't want to give up the lightweight, fast defaults they have. Even Rust's canonical random library has an XorShiftRng. These are what PCG is competing with, and replacing all those weak RNGs with PGC RNGs would make them all much better.