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.
Or humans make a mistake. I got burned by the MsDos date rollover with signed values ~20 years ago. A salesman fat-fingered a job into the 2060s. Of course while I was on the other side of the world with no phone access.
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).
The St Nicholas Orthodox church sat at the base of the Twin Towers, because it was there for 100 years and they wouldn't take the money to rebuild it elsewhere. They probably served their last Divine Liturgy there on Sunday 9/9/01 as a last blessing before it was destroyed that Tuesday.
I was on a break at work reading a lot about 9/11 for some reason. Went back to fix an easy bug where our timestamps were printing wrong dates (milliseconds vs seconds) so I became curious what dates would show up if I added zeros in front of 1, to get a ballpark of where dates are. I freaked out after the ninth zero, you know, being so close to the event I was just reading about.