5 ms·
> A UUID alternative like a73ba12d-1d8b-2516-3aee-4b15e563a835 is just wasteful from an user’s perspective. The argumentation in this article is pretty poor fr
by siva7 3y ago
> A UUID alternative like a73ba12d-1d8b-2516-3aee-4b15e563a835 is just wasteful from an user’s perspective.
The argumentation in this article is pretty poor from my experience. A UUID isn’t meant to be handled by the non-technical end user. The end user usually doesn’t and shouldn’t care about the URL. I can assure there are bigger architectural problems in your design if your user has to care about accessible internal ids.
- olalonde 3y agoDoes this help see what's wrong with UUIDs in URLs? A GitHub issue URL in a parallel universe: https://github.com/a73ba12d-1d8b-2516-3aee-4b15e563a835/e16957bf-7d7f-41f1-97f4-98c93a6c3540/issues/4e4e9133-bcdb-45b9-8dfe-9e951846e3c6
- siva7 3y agoI see bad url design for other reasons but nothing wrong with UUIDs, so no it doesn’t help me see the argument.
- olalonde 3y agoWhat do you mean by bad url design? Because it's using UUIDs? That was my point.
- JaredCliff 3y agoNot OP but it's obvious to me that by bad url design, they mean that you could have used usernames and issue numbers in the URL but you chose to go with random IDs where there was no need for it.
- j-pb 3y agoA fairer comparison would be that in that universe the url would be: https://github.com/4e4e9133-bcdb-45b9-8dfe-9e951846e3c6 or even urn:uuid:4e4e9133-bcdb-45b9-8dfe-9e951846e3c6 with the right infrastructure.
- RamblingCTO 3y agoAbsolutely. The issue uuid should then be a UUIDv5 namespaced to the context and you only have one globally unique id. I think people just don't understand uuids properly and treat them as a "gives me some random thingy".