On the other hand, using a 64 bit integer to count seconds moves the problem 292 billion years forward, and we can probably let the Omega Point handle it from there.
On the other other hand, getting greedy and using a 64 bit integer to count nanoseconds only moves the problem 448 years forwards. That's long enough to seem like it's perfectly safe, but short enough that it might just not be.
doing it that way would be better writing
libuv, which sits underneath node.js, uses 64-bit nanosecond timestamps. And by that time, everything will be javascript.