4 ms·

We maintain a couple of popular ksuid libraries[1][2] and use it, so we definitely like ksuid. Though one big issue with ksuid is that being 160bit means that i

by tasn 3y ago

We maintain a couple of popular ksuid libraries[1][2] and use it, so we definitely like ksuid. Though one big issue with ksuid is that being 160bit means that it doesn't fit into native uuid types in databases (e.g. postgres), which means that they come with a performance penalty. 1: https://github.com/svix/rust-ksuid https://github.com/svix/rust-ksuid 2: https://github.com/svix/python-ksuid https://github.com/svix/python-ksuid

Xeoncross 3y ago
I'm curious, why do you not store these as binary data or do you and you're saying that the UUID operations are better optimized than sorts on binary data?
- snuxoll 3y ago
  I can compare a 128bit UUID in a single instruction, a 160-bit ksuid is a little weirder to work with at the hardware level.
- tasn 3y ago
  Exactly what the sibling said, and the same applies to database operations (when they have a uuid type).