2 ms·

Some discussion here: https://github.com/uuidjs/uuid/issues/546 https://github.com/uuidjs/uuid/issues/546 Eg: > FWIW, I just tested crypto.getRandomValues()

by e12e 5mo ago

Some discussion here: https://github.com/uuidjs/uuid/issues/546 https://github.com/uuidjs/uuid/issues/546 Eg: > FWIW, I just tested crypto.getRandomValues() behavior on googlebot and it is also deterministic(!)

D2OQZG8l5BI1S06 5mo ago
That makes sense. I'm not sure why anybody would generate UUIDs in browsers though, it seems to defeat the purpose.
- danpalmer 5mo ago
  Tell that to Segment. Hopefully they've fixed that, but they didn't seem to think it was a problem years ago (spoiler: it was a big problem).
- perlgeek 5mo ago
  When you do CQRS, you basically have to generate some form of unique identifier in the client. Why not a UUID in the browser?
- dylanhouli 5mo ago
  > I'm not sure why anybody would generate UUIDs in browsers though, it seems to defeat the purpose. How about for offline-first apps?