Why not?
-
I worked on a project once that represented time-of-day as a 4-digit number. 0000 was null and 2400 was midnight. It allowed all sorts of invalid values like 1075 or 3000. Doing any kind of math, even just generating a human-formatted string was really painful
The problem with epoch + counter is that it can become inaccurate for dates in the future. If I were designing something that had to store time, I'd personally structure it as (i64 for days, i64 for nanos) -- or (i32 for days, i32 for micros) if space was that big of a concern
-
-
"days" and "subsecond thingy" being offsets from an epoch of course. You need days to be separate in order to represent dates in the future accurately though
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.