From a practical standpoint, isn't it usually the case that there are retention periods for traces given how numerous they can be?
I bring this up because this article starts with "I asked Claude", but it doesn't explore the the length of time you're generating IDs over at all, which is an important aspect to consider when selecting size.
Surprised the author didn't even think about the logical conclusion of his closing paragraph: "128 bits is the ideal sweet spot, collision safety effectively forever, and it happens to match the size of a UUID, which means every database, every language, and every protocol already knows how to handle it."
UUIDs are already generated randomly for exactly the same reason. Rather than inventing something new, they should have just used a UUID.
4 comments
[ 3.9 ms ] story [ 14.6 ms ] threadI bring this up because this article starts with "I asked Claude", but it doesn't explore the the length of time you're generating IDs over at all, which is an important aspect to consider when selecting size.
UUIDs are already generated randomly for exactly the same reason. Rather than inventing something new, they should have just used a UUID.