You’ve literally just shifted the problem, those two businessmen now have to both figure out what hour their daily cycle starts on, to assess if they will be free or not during the time. The idea of “business hours” would just be “so what hours on the 24h clock are you ‘at work’ at?'”
Except when you lived in that zone you’d instinctively know the local hours within a week of the change. So you just need to tell the other guy “I’m working from 0300 to 1100 tomorrow, when are you free?” Without worrying which time zone to reference.
It also would give a path to abolishing DST, since the main reason it still exists is “because other places so it”. Using a global time would allow local areas to implement DST or not based on their own preference, without affecting anyone else. I believe this would quickly lead to most places abolishing it.
Note that I live in Saskatchewan, one of the few DST-free zones in the world (well actually permanent DST, as we joined the time zone to our west) and it’s annoying that the rest of the world is always goofing around with their clocks. It’s one of those literally pointless traditions from the days of gas lamps.
That is about as simplistic as a model as I can possibly give… now imagine the logistics of that bullshit when dealing with multiple time zones and actual transit times lol.
You can lament the fact that you’re trying to be kind and figure out a good time for a call in such a situation when there’s NEVER going to be a good one anyway.
With this, it takes out EVERY extra timezone calculation for shipping, receiving, internet clocks, code regarding time difference variables. SO MUCH.
Ugh, I HATE the pointless code required by the stupid time locales, DST, and how many languages force you to play along with it all when all you really wanted was an emulated hardware RTC so you could schedule a task to run 10 minutes from now.
You’ve literally just shifted the problem, those two businessmen now have to both figure out what hour their daily cycle starts on, to assess if they will be free or not during the time. The idea of “business hours” would just be “so what hours on the 24h clock are you ‘at work’ at?'”
Same problem, different calculation.
Except when you lived in that zone you’d instinctively know the local hours within a week of the change. So you just need to tell the other guy “I’m working from 0300 to 1100 tomorrow, when are you free?” Without worrying which time zone to reference.
It also would give a path to abolishing DST, since the main reason it still exists is “because other places so it”. Using a global time would allow local areas to implement DST or not based on their own preference, without affecting anyone else. I believe this would quickly lead to most places abolishing it.
Note that I live in Saskatchewan, one of the few DST-free zones in the world (well actually permanent DST, as we joined the time zone to our west) and it’s annoying that the rest of the world is always goofing around with their clocks. It’s one of those literally pointless traditions from the days of gas lamps.
That is about as simplistic as a model as I can possibly give… now imagine the logistics of that bullshit when dealing with multiple time zones and actual transit times lol.
You can lament the fact that you’re trying to be kind and figure out a good time for a call in such a situation when there’s NEVER going to be a good one anyway.
With this, it takes out EVERY extra timezone calculation for shipping, receiving, internet clocks, code regarding time difference variables. SO MUCH.
Ugh, I HATE the pointless code required by the stupid time locales, DST, and how many languages force you to play along with it all when all you really wanted was an emulated hardware RTC so you could schedule a task to run 10 minutes from now.