Rating: 2.71 | Rated! (Hint: Use number keys to rate)
Comment: (Prefer English language)
09.05.2026 - 17:07:53 <anon> Nerd shit
09.05.2026 - 17:13:15 <anon> someone felt it was important to share this...
09.05.2026 - 17:15:18 <anon> yes because UUID stands for "universally unique indentifier" meaning you should not be able to generate 2 of the same. Ever.
09.05.2026 - 17:19:06 <anon> WTF, just user microseconds since 01.01.1970
09.05.2026 - 18:05:16 <anon> "startup" "maybe 200 devs" "in his first week", and all the rest is too contrived as well. total BS story.
09.05.2026 - 18:13:19 <anon> "The probability of a collision with a randomly generated UUID (version 4) is extremely low, approximately 1 in 2.71 x 10^18. This means that even generating a billion UUIDs per second for 85 years would only give a 50% chance of a collision occurring." The probability of, for example, error when stored on disk, or when transferred over a network, is hugely higher than this.
09.05.2026 - 18:39:56 <anon> tldr people at a startup don't understand fundamental concept of UUID, pay multiple full time salaries for something a single line of code can do
09.05.2026 - 19:33:00 <anon> what
10.05.2026 - 00:35:51 <anon> They aren't magically unique. There was literally a collision at a very small number of reps documented on HN yesterday: https://news.ycombinator.com/item?id=48060054. Maybe the UUID oracle discussed here was devs faffing on company time, but it's also totally plausible they'd had real collisions across nodes and needed to open up the walls to get the voices out.
10.05.2026 - 01:00:47 <anon> fuck reddit crossposting. fuck it