This just kind of proves GP's point. Random APIs usually tell you what the RNG is, but not the why/how. Most people don't care if it's /dev/(u)random, Mersenne

This just kind of proves GP's point. Random APIs usually tell you what the RNG is, but not the why/how. Most people don't care if it's /dev/(u)random, Mersenne twister, PCG, LFSR, LCG, RDRAND, etc. They care about roughly 4 attributes: - Is it good for crypto - Is it fast - Is it reproducible - Is it portable But fundamentally, it's about the use case and interface: - I need secure random (strong, slow, secure) - I need Monte Carlo (good enough, fast, reproducible) - I need chaotic behavior for my game/stress test/back off protocol (usually can be barely random, fast, reproducible) I think calling the last case InsecureRandom or RandomEnough is reasonable to convey "don't use me for secure purposes".