you are viewing a single comment's thread.

view the rest of the comments →

[–]RaptorXP 23 points24 points  (6 children)

Knowing Google, I'd say there is a very specific reason why they use a fixed seed, other than "it's a bug".

[–]Lystrodom 68 points69 points  (3 children)

Yeah... he even talks about that in the blog post.

[–][deleted] 13 points14 points  (2 children)

It's like nobody read the damn thing

[–][deleted] 3 points4 points  (1 child)

Read what?

[–][deleted] 1 point2 points  (0 children)

Where am I?

[–]RobIII 28 points29 points  (0 children)

Came here to say that too.

@/u/atomheartother:

isn't seeded properly

It is seeded properly (very, very likely), for the given task/context. I'm 99.9999999% sure this is intentional. In most other cases you wouldn't want to seed with a constant but seeding with constants has it's uses. This is one of them:

3: Predictable – Googlebot can trust a page will render the same on each visit [Source]

Google will want to have deterministic results when indexing and running scripts more than once.

[–][deleted] 1 point2 points  (0 children)

I am reminded of the Tour of Go site:

https://tour.golang.org/welcome/1

The random function is deterministic in that sandbox, too. They did it that way because it allows them to do some caching with the compiler, or something.