> "I woke up at 9 this morning",
Yes you do, you know he woke up possibly a little late, but didn't massively oversleep.
> "I woke up at 22 hours this morning,
Now I have no idea whether that's good/bad/early/late without a lookup table.
Re:Time to Dump Time Zones
by tom_mellior on Monday November 07, 2016 @06:29AM
(#12890294)
> Yes you do, you know he woke up possibly a little late, but didn't massively oversleep.
As I tried to illustrate in the rest of my post, there are a lot of (cultural, and other) assumptions that go into this. If they are usually at work at 8, then sleeping until 9 is pretty massive, especially if a long commute is involved.
Do you really? If your friend called, said "I woke up at 9 this morning", then hung up, you wouldn't really know what that means.
Usually your friend would embed this information in some context, like "I woke up at 9 this morning, but I had an important meeting scheduled for 9:30, and my commute takes at least 30 minutes even on the best days. Oops." You need this amount of context to understand what they are really trying to tell you, and you wouldn't keep track of your friends' schedules and commute times at this level of detail.
But if the context is provided, the actual number doesn't matter: "I woke up at 22 hours this morning, but I had an important meeting scheduled for 22:30, and my commute takes at least 30 minutes even on the best days. Oops." conveys exactly the same information.
More generally, my colleagues and me might come in to work at any time between 8 and 10 in the morning, and I guess (but don't check!) that that's the same for my friends in other companies. So if a random friend tells me "I woke up at 9 this morning", they could mean anything between "... and I realized I would be at work two hours later than usual" and "... so I would have time to feed the ducks in the park on the way to work and still be at the office before the boss".