News for hackers. Stuff that matters.

A comment on /story/36037607. Parent comment

Re: by quickthrower2 on Tuesday May 23, 2023 @12:16AM (#36039762)
Yes, the obvious case is machine learning, so that you can make changes and run your program again, and it uses the same batches as so forth.

Another case are unit tests with random-generated cases. At a minimum you want to know the seed of the last run and have that reported. On CI system you would want it to be deterministic.

Where you want there not to be a seed is in crypto, or possibly a game like poker or even tetris.

[ Parent | on HN ]
Re: by explaininjs on Tuesday May 23, 2023 @06:32AM (#36042277)
I’d argue that in poker you must use seeded randomness — but everyone has to contribute to the random “pool”. This is the only way I know of to have effectively random values with zero trust.
[ Parent | on HN ]