4 ms·
There's no mention of the UUID v7 in the README. Based on my basic understanding, v7 uses the first 48 bits to encode the Unix epoch, which makes them more usef
by martinrue 2y ago
There's no mention of the UUID v7 in the README. Based on my basic understanding, v7 uses the first 48 bits to encode the Unix epoch, which makes them more useful for sort/indexing scenarios. Might be useful to compare ULID and v7 in the README to make it clearer the benefits one has over the other.
- sakjur 2y agoDigging into the discussions in the repo’s issues, I found someone linking to this comparison between ULIDs and UUIDs: https://uuid.ramsey.dev/en/stable/rfc4122/version7.html https://uuid.ramsey.dev/en/stable/rfc4122/version7.html In short, it seems UUIDv7 is storage-wise compatible with ULID but not vice versa due to UUID’s versioning bits.
- laserbeam 2y agoThere’s no mention because this is 5-7 years old. I believe that predates UUID 6-8.
- martinrue 2y agoYou know, I didn't even look at the last commit! I assumed it was a new thing, and hence why it was being shared now. Here's an idea for HN: when processing a repo link, auto add (<time since last commit>) to the end of the title.
- dotancohen 2y agoGood idea, but in my opinion that information really only needs to be added if it is significantly long ago, such as when appending a parenthesized year to a title.
- martinrue 2y agoAgreed. If the thing hasn't seen a commit in say 3 years, it'd be useful for idiots like me to know before they assume it's new because it's being shared now. Still, my bad :)
- linkdd 2y agoThat would not convey the information "does this predate $X?", because an older tech could still be maintained daily.
- neya 2y ago2019 is 5 years ago? Wow. Time flies.
- jakjak123 2y agoThis is several years old. I used it first in 2019