3 ms·
UUID also suffers from a serious issue: there is no standard way to encode them as string and in binary format. In binary, UUID can be encoded as Big Endian or
by unscaled 4y ago
UUID also suffers from a serious issue: there is no standard way to encode them as string and in binary format.
In binary, UUID can be encoded as Big Endian or Little Endian or even Mixed Endian, and while the string encoding is usually lowercase with a certain hyphenization rules, I've seen variations of that.
The (hexadecimal) text encoding is also quite inefficient compared to more modern standards like ULID or kSUID.
- masklinn 4y ago> In binary, UUID can be encoded as Big Endian or Little Endian or even Mixed Endian RFC 4122 section 4.1.2: > The fields are presented with the most significant one first. > while the string encoding is usually lowercase with a certain hyphenization rules, I've seen variations of that. RFC 4122 section 3: > The hexadecimal values "a" through "f" are output as lower case characters and are case insensitive on input. The hyphenation is normative, per the same section UUID = time-low "-" time-mid "-" time-high-and-version "-" clock-seq-and-reserved clock-seq-low "-" node