brain VS ulid

for those researching this topic, I keep a list of these UUID/GUID implementations!

https://github.com/swyxio/brain/blob/master/R%20-%20Dev%20No...

here are my notes as someone who studied this stuff extensively for my book launch (just crossed $200k revenue) https://github.com/sw-yx/brain/blob/906dbc6fd6d22fa69968ebc6...

in generally for OP's stuff i would disagree on launching on product hunt first. PH is a giant pyramid scheme where people just compete for the #1 badge each day. what the most successful products do is launch everywhere else first, and then after a few months email their happy customers to support them on PH. this is why you are #20 because you didnt study the game

I've been collecting all my notes on UUIDs here https://github.com/sw-yx/brain/blob/master/R%20-%20Dev%20Not... in case it is helpful to anyone

(poster here)

these formats are not new new, but are still pretty new.

the context is i keep a list of uuid impls and knowledge for my own reference. posted this up today simply because I got a PR from some subscribers https://github.com/sw-yx/brain/pull/36

Putting together this massive effort involved pulling in notes from 18 months of covering Concurrent React by myself, in particular studying prior art from Rodrigo Pombo in cloning the API from scratch. You can check out his talk here to contrast what he did vs me.

I really like ULID for this problem (e.g: https://github.com/ahawker/ulid)

- same number of bytes as UUID

- start with a date, so has great locality. Plus you get extra information in the uid that you can extract.

- can be created from an existing date or uuid, and exported to a uuid, so there is a migration path

As the author of a popular ULID implementation in python[1], the spec has no stewardship anymore. The specification repo[2] has plenty of open issues and no real guidance or communication beyond language implementation authors discussing corner cases. The monotonic functionality is ambiguous (at best) and is implemented differently per-languages [3].

Functionality, UUIDv7 might be the _same_ but the hope would be for a more rigid specification for interoperability.

[1]: https://github.com/ahawker/ulid

[2]: https://github.com/ulid/spec

[3]: https://github.com/ulid/spec/issues/11

Looks similar to ULID[0] (I am the author of a popular python implementation[1]).

It appears to have a similar constraint that two ID's generated within the same timestamp (ms, ns) have no strong guarantee of ordering. That might not be a deal breaker depending on your use case but something to consider.

* https://github.com/ulid/spec

* https://github.com/ahawker/ulid