Have any of you ever spent so much time with fundamentalists that you started thinking characters from the Bible decided to read the Bible itself to figure out what they had to do next? FUCK THE RECURSIVE BIBLE! Also, days were less than 24 hours long in the distant past, "red" was sometimes used in the Bible to describe brown objects, and most Bible-thumpers might secretly be porn addicts.
>Also, days were less than 24 hours long in the distant past
Worth noting that much of that past was millions of years ago. A past which people like young earth creationists to this day staunchly believe never happened.
Google says that day length in the Jurassic was between 22 and 23 hours. In the Paleozoic, it was probably closer to 20. For as long as humans have been around, the minute increase in day length during that time should have been entirely unnoticeable.
That's all pretty arbitrary. During the French Revolution, decimal time was briefly introduced in France, where every minute had 100 seconds, every hour 100 minutes, and the entire day had ten hours. One second in decimal time would equate about 1,15 seconds in 24-hour time.
There are decimal watches today, but they're very niche.
I have no idea what this is, but one of my own gripes with the extremely religious is that it's a sin to claim, or even personally believe, that you can fully understand the infinite truth of God. So no matter how much you read the Bible, you're always going to misunderstand it. So don't be extreme about it.
Well, at least the Bible is free. If you look at Scientology, you're taken to the cleaner's for potentially hundreds of thousands of dollars in seminar and auditing fees, and at the end of it, the "truth" about the Universe that is revealed to you as you become an Operating Thetan is nothing but tall tales and shite ramblings of a second-rate sci fi author.
Internally, most computer systems keep time by counting the number of seconds since midnight on the 1st of January 1970. It's not a very convenient unit for humans, but it's much easier and less error prone than constantly having to convert back-and-forth between different time zones.
For database transactions it rarely matters exactly when something happened, as long as all of the transactions are in precisely the right chronological order. There are loads of oddities to normal timekeeping that most people don't pay attention to - different countries start and end daylight savings at different times, some countries don't use the Gregorian calendar, sometimes the borders of time zones change and there are occasional leap seconds to account for the fact that a day isn't exactly 24 hours long.
>>451891 >having to convert back-and-forth between different time zones.
Out of curiosity, which timezone did they use for the 1/1/70 midnight start time? It wasn't midnight everywhere at once; is it California time? Our time?
Nah, if you need really accurate distributed time (because your experiment is hundreds of kilometers across and you care about times in the nanosecond range or less), you want something like white rabbit - accurate to ns, precise to ps,
https://white-rabbit.web.cern.ch glorious madness. None of this pissing about with time zones - is the time at your head the same as the time at your toes? Light takes a while to get there, does time?