I wrote Yet Another UUID [1] for my own purposes recently as well.  Mine&#x27;s based on Firebase&#x27;s style UIDs [2] -- they sort roughly chronologically, because operationally, I find that irritates me less.  Arbitrary choice?  Entirely.  Regrets?  None.  Do I recommend it for use?  Also not at all.  Unless you feel like it.  It&#x27;s fine.  I guess.<p>I&#x27;ve kind of given up on there being any purpose to a One True Spec for UUIDs.  Count how many bits of entropy you want.  Shove some CSPRNG into it.  Call it a day.<p>¯\_(ツ)_&#x2F;¯<p>(This a fine implementation, fwiw.  I only mean to share my honest question as to whether there&#x27;s any real utility to UUIDs-as-a-library.)<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;polydawn&#x2F;repeatr&#x2F;blob&#x2F;dd41ca72421a173b5aa14580f5d7df48df1548d0&#x2F;lib&#x2F;guid&#x2F;guid.go" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;polydawn&#x2F;repeatr&#x2F;blob&#x2F;dd41ca72421a173b5aa...</a>
[2] <a href="https:&#x2F;&#x2F;www.firebase.com&#x2F;blog&#x2F;2015-02-11-firebase-unique-identifiers.html" rel="nofollow">https:&#x2F;&#x2F;www.firebase.com&#x2F;blog&#x2F;2015-02-11-firebase-unique-ide...</a>