2 ms·
Still only pushes the problem back for an additional 100k years. If they were really serious they’d use prefix codes. :P
by taneq 7y ago
Still only pushes the problem back for an additional 100k years. If they were really serious they’d use prefix codes. :P
- posnet 7y agoI am more worried about what we will do when we run out of 64 bit seconds for unix time. 500 billion years is barely half way through the star forming age of the universe.
- deleted 7y ago[deleted]
- Dylan16807 7y agoWell, timespec does have 34 bits it's not using...
- Arcorann 7y agoRFC 2550 (https://tools.ietf.org/html/rfc2550 https://tools.ietf.org/html/rfc2550) remains one of my favourite April Fools' RFCs. It even has support for negative dates.
- iso1210 7y agoThat seems like a needlessly complex way to store datetime Dark era starts in 10^106 years time, or about 10^157 plank times, so any time can be respresented in 20 bytes. Just 44 bytes will allow encoding of any point in spacetime, and they are using far more than that to simply encode years.
- hexane360 7y agoThe RFC admits that and then says: >2.4.2 Transcending Environmental Considerations >However, we might get lucky. So, Y10K dates are able to represent any possible time without any limits to their range either in the past or future.