time

javajosh 2023

The Year 2038 problem is when "32-bits of milliseconds since the 1970 epoch" runs out.

Interestingly, Javascript with Date.now() and +new Date()

Here is an interesting Stack Overflow discussion of using 53-bits of a Javascript float as a timestamp. So, it is probably that Javascript runtimes that rely on a ms-since-epoch timestamp will be okay for a couple hundred thousand more years. Which is nice overhead.