Earlier quoted context omitted.
But is that the apocalypse? I hate the fact that we're destabilizing the environment, but humans (and wildlife) are pretty good at adaptation. Our ancestors have obviously survived massive extinction events in the past.
Yes, obviously, but our ancestors weren't human then.
Doomsday scoreboard
121–130 of 167 posts
Re: Doomsday scoreboard
#122Earlier quoted context omitted.
The homeless man currently yelling outside my window is an equally authoritative source of information about the apocalypse as the Bible, and he thinks it's coming soon.
A billion people don't believe there's some truth to what the homeless man outside of your window is saying, and someone leading a legitimate-enough revolution that they're put to death by the King of Rome is probably a tiny bit more believable. But I get what you're saying either way. I just think it's an interesting factlet.
Re: Doomsday scoreboard
#123Earlier quoted context omitted.
Its systematic theology is internally consistent; amazingly consistent given three thousand years across 66 books and dozens of authors. It’s the cherry picking and overemphas that gets one into trouble
>Its systematic theology is internally consistent It's not. Christian dogma doesn't even obey the law of identity.
Re: Doomsday scoreboard
#124Earlier quoted context omitted.
9/11 happened 1 trillion milliseconds after the unix epoch.
Then I am a victim of the Mandela Effect because I can clearly remember (time_t)1e9 happening earlier than that. I've checked https://en.wikipedia.org/wiki/Time_formatting_and_storage_bu... and I can't see what I could be muddling it up with, either. Spooky!
Re: Doomsday scoreboard
#125Earlier quoted context omitted.
9/11 happened 1 trillion milliseconds after the unix epoch.
Who finds this shit out lol
Re: Doomsday scoreboard
#126Re: Doomsday scoreboard
#127Earlier quoted context omitted.
9/11 happened 1 trillion milliseconds after the unix epoch.
Not quite; the first attack happened at approximately UNIX time 1000210380, which isn't quite as round as "1 trillion milliseconds". (It was about 2 days after 1e9).
Re: Doomsday scoreboard
#128Earlier quoted context omitted.
The book of Revelation also cites various signs that are metaphorical enough to be applied to just about anything. It's pointless to cite the Bible to defend a theological position, because someone else can cite a different part that can be interpreted to say the exact opposite.
That's why the Catholics have a guy in charge who infallibly tells you how to interpret the damn thing. Instead of having every Tom, Dick and Harry have a stab at misunderstanding scripture.
Re: Doomsday scoreboard
#129One mildly interesting fact that MANY Christians get wrong: There is no lead-up to the apocalypse. The Messiah will return "like a thief in the night" and "nobody, except my Father, knows the hour of my return" (I probably butchered those two quotes). Either way, the Bible is pretty clear (as was Jesus): there will be zero indication the apocalypse is coming. None. It'll just... start.
One mildly interesting fact MANY programmers get wrong about the is_computer_on function: It is threadsafe. The documentation is very clear about this.
Re: Doomsday scoreboard
#130Earlier quoted context omitted.
Right, but there's no doomsday prophecies around the Year 2038 problem as far as I can tell. I think it falls in the same kind of category of known problems that are certain to happen at some point. Some other things I was thinking of were the theorized ARkStorm, and also an earthquake that could happen in the Cascadia subduction zone.
It's also not impacting _only_ at that time, many tasks involve dates in the future, and a system dealing with a far enough off date _today_ is already impacted. So it's not as if "everything works" then suddenly "everything doesn't" And it's only for operations that care about the sign / compute deltas / use signed numbers, otherwise it's 2106-02-07 06:28:16 UTC.