You Don't Need UUID
henvic.dev
You Don't Need UUID
1–10 of 199 posts
Re: You Don't Need UUID
#2Re: You Don't Need UUID
#3Does it make the URL in the URL bar longer? Yeah, but does that matter?
Re: You Don't Need UUID
#4I would challenge the premise we appear to be starting from, that the average end user cares to be dealing with any random string of numbers and digits. GUIDs work well, they’re implemented everywhere, and you won’t find out long after you go into production you made some mistake that is going to make it so you have to migrate away from them.
Re: You Don't Need UUID
#5Re: You Don't Need UUID
#6That's a terrible way to use it is all.
Re: You Don't Need UUID
#7They will be in a deterministic order, but will appear semi-random to the end user.
For things like product IDs or user IDs, etc you don't actually need them to be random. But perhaps you don't want them to simply start counting sequentially.
Re: You Don't Need UUID
#8In particular databases (where UUIDs taking space was a big concern) they have largely switched to a packed binary format that makes the size of UUIDs over time a non issue for all practical purposes.
Re: You Don't Need UUID
#9When it comes to random identifiers, the advantage of uuid4 is mainly that it's a standard thing that everyone understands well, and finding a lib that generates one securely won't require any thought. It's never the ideal solution, but it's often good enough.
Re: You Don't Need UUID
#10The crux of this argument seems to be that UUIDs are too long? Which I disagree with. I can't memorize them, no, and it would be cumbersome to try to say one aloud, but these aren't situations I've ever found myself in. Does it make the URL in the URL bar longer? Yeah, but does that matter?