They should make the versions UUIDs instead of integers so that we don't make assumptions about their ordinal relationships.
Programming
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
Or maybe an abbreviated hash of the text of their specifications?
Yea, should have been V-00000000-0000-0000-0000-000000000008
instead
Yes and no. They had to put the version identifier somewhere to avoid sorting problems or parsing problems, so I think that putting somewhat in the middle is a good tradeoff.
A lot of people in this thread who don't fully understand how UUIDs work...
You're not kidding.
I didn't even know it was an ietf standard. Let aline there were versions. Apparently it's only since may this year that there are 8 versions. Before it were only 5.
Reject UUID embrace ULID.
At the company I work at we use UUIDv7 but base63 encoded I believe. This gives you fairly short ids (16 chars iirc, it includes lowercase letters) that are also sortable.
base63? I'd guess you'd mean base64?
Anyways, doesn't that fuck with performance?
I'm using this in production: RT.Comb - That still generates GUIDs, but generates them sequential over time. Gives you both the benefits of sequential ids, and also the benefits of sequential keys. I haven't had any issues or collisions with that
It's Base62 actually, misremembered that. It's to avoid some special characters iirc. And no, performance is fine.
We're using this: https://github.com/TheArchitectDev/Architect.Identities
I'll be borrowing that little trick
https://github.com/TheArchitectDev/Architect.Identities
Here's the package one of our former developers created. It has some advantages and some drawbacks, but overall it's been quite a treat to work with!
I prefer CUID
Just to clarify: Yes, I do know not all use cases are appropriate for CUID. But in general when generating ID, I'd use CUID2
I vote for nanoid.