Why don't we format Unix timestamps like we do with IPv4 addresses? They are both just 32 bit integers.
"Hey, what time is it?" - "Oh, it's 103.1.0.185."
It even works for time ranges!
"The conference will be held in 103.1.0.0/19"
Why don't we format Unix timestamps like we do with IPv4 addresses? They are both just 32 bit integers. "Hey, what time is it?" - "Oh, it's 103.1.0.185." It even works for time ranges! 22 comments
@r5 I'm now busy trying to work out what I'd use a netmask for :-) @r5 Hmm, a mask could make every other period of 34mins 8secs unavailable for meetings, so that nobody could steal more than about ½ hour, and even then only if they were really keen to have me :-) @r5 32bit time_t fails in 2038 though. I propose timev6.. we can up the granularity to milliseconds as well, so it's currently 0000:0192:5CBB:447D and that won't run out for centuries. @r5 What’s wrong with just using milliseconds since 1 January 1970 (sorry, I mean 0). @r5 a cursed suggestion; but slightly less cursed than Swatch Internet Time @r5 Decimal binary time, hm? |
@r5 Thanks, I hate it. :D