I don’t see how, unless you want to redefine “year” as something other than one revolution around the sun and “day” as something other than one rotation of the planet. I think the idea of letting or time bases drift away from the cycles we find meaningful and useful to us is rather counterproductive.
I never thought of that. But then I was never onboard with this whole concept to begin with. It seems like it’s only for the convenience of programmers, well boo hoo. I’m not even sure that it would help them all that much. There’s plenty of things we do that are tied to place and the time of day relative to the position of the sun, and with everyone on the same clock you’d still need a relative time zone or GPS coordinates and a way to define “this is the operating time I want to be in”. For something as simple as opening hours for a nationwide business, you can’t say 9-5 anymore. It’d be 900-1700 in this arbitrarily defined zone, 1000-1800 in this other arbitrarily defined zone, etc. Say you’re putting together a kitchen schedule for all your restaurants. It’s no longer possible to say “start prepping breakfast at 5am for opening at 7am” or whatever, because those times are now different depending on the location. For every problem this solves I suspect there’s a new problem that it introduces.
Trivial to change perhaps, but I’d argue there’s more mental processing required. Not so much from an email signature or corporate website standpoint, but from a “figuring it out” standpoint. Right now if you need to contact someone across the world, all you really need to ask is “what time is it there now”? That’s easily retrievable, and you can make a note of “they’re X hours behind/ahead of us”. Under the proposed system, you instead need to ask “what are the standard business hours there” or “what is the equivalent standard 9-5 time block there”?
Point being, for many practical uses, you end up falling back to some sort of time zone.