Live data from Hacker News

Use Timestamps

jankremer.eu

161–163 of 163 posts

Re: Use Timestamps

#161

Earlier quoted context omitted.

Nothing in the solar system has a relative speed different enough to earth to make common timestamps different - the difference is well below leap second impacts. As for simultaneity we already have to deal with that at the millisecond level. An event logged at 16:00:01.000 as far as LA is concerned maybe logged at 16:00:01.080 in London, or maybe at 16:00:00.920

I mean the clocks on different planets do tick at slightly rates. It's somewhere on the order of milliseconds per year, except for really large planets, but it does add up

Yea, same as clocks in orbiting satellites, or even difference in rates between different locations on earth.

The difference is negligible compared to leap seconds.

Re: Use Timestamps

#162

Earlier quoted context omitted.

> And now open a contemporary smart phone interface, and show me, without any special tooling, the actual, "physical" file system. Yes, I had phones in mind when writting the above :) > And these things are probably the most successful consumer computing platforms ever. Users don't have better choice in this market.

Why do you think Apple and Google hide the file system in their mobile OSes? Just for fun?..

I could name several hypotheses, but I don't know exactly.

What I am certain of, is that it's very inconvenient to not have access to file systems.

Re: Use Timestamps

#163

Earlier quoted context omitted.

You still have to calculate the distance between a date on the DB and a date on the client, the timezone difficult issues are not sidestepped at all

Your server and DB are both UTC. If not, that's something you just need to fix. The server can then calculate the difference trivially. Then you no longer need to do anything on the client. Eg, this is what Django's timesince or timeuntil filters do: https://docs.djangoproject.com/en/4.2/ref/templates/builtins...

[deleted]
Post reply on HN