Show HN: JSONlite – A simple, serverless, zero-configuration JSON document store

Re:Show HN: JSONlite – A simple, serverless, zero-configurat... by CJefferson on Sunday February 12, 2017 @10:33AM (#13628778)

With 1, you are trusting the directory returned by uuid will be unique --it should be, but it might not be, in particular if it is based on time and I run in two threads.

With 4, I find once a directory has about 100,000 files in it, things get bad, from the simple (ls * won't work) to the nastier (git starts using huge amounts of space, you'll hit github's size limit even though all your files are quite small).

[ Parent | on HN ]

Re:Show HN: JSONlite – A simple, serverless, zero-configurat... by sz4kerto on Sunday February 12, 2017 @12:13PM (#13629275)

I would not let anyone close to the code I'm working on if he wanted to verify whether a properly generated UUID clashes with some previously generated UUID.

You could just as do stuff like "int x=1; assert(x == 1);" and so on. And it would be just as futile.

[ Parent | on HN ]

Re:Show HN: JSONlite – A simple, serverless, zero-configurat... by CJefferson on Sunday February 12, 2017 @12:18PM (#13629298)

In this case, you are relying on what installed program or function is called when you invoke uuid in the shell. It seems reasonable to me to check if it is having sensibly, if the reliability of your program counts on it. I have no idea what dodgy uuid programs you might find installed.

[ Parent | on HN ]

Re:Show HN: JSONlite – A simple, serverless, zero-configurat... by avip on Sunday February 12, 2017 @11:39AM (#13629086)

In all fairness, I find this (and only this) criticism unsubstantiated/nitpicky.

Many systems are relying on the statistical improbability of 32-hexdigits uuid collision (name-dropping one - Disque).

[ Parent | on HN ]