Sounds great in theory, but it becomes too hard to know what times are "early" and "late" for people. When telling people what time it is, you'd also have to include where you are so they know what's early/late, and at that point you've just reinvented timezones.
Yeah, of course there are trade offs, and that's not a balanced run down of them. Most of the issues raised there seem easily addressed in the modern world.
agreed! based on the amount of "time" i've wasted converting timezones in code, i tell everyone that'd listen we should just teach kids to memorize unix timestamps and these problems would all go away
