Indeed. There's a tradeoff in both directions - either you trust the cloud^W grid, or you trust your local clock, and both of them have failure modes; there's no one clearly superior option here. You could combine them, but then it gets complex in short order.

> I mean, in software engineering we try to avoid unnecessary dependencies right?

I/you wish.

> in software engineering we try to avoid unnecessary dependencies

leftpad would like to have a word

Putting Lego blocks together is engineering now?

Edit: NPM has engineering challenges, and Node as well...but I would be extremely hesitant to call a library of ~ten LoC "engineering."

i'm not a fan of what the JS ecosystem looks like, but you can and will get bitten by transitive dependencies if you don't store them all in a local mirror that doesn't respect upstream deletions...

Of course. But that's an engineering problem worthy of the name (cache-invalidation and whatnot).