Comment

Comment on Jragon

blanketswithsmallpox@lemmy.world ⁨7⁩ ⁨months⁩ ago

The time zone thing means if the time on your clock reads 00:00 hours, it’s 00:00 hours everywhere.

That means if I say I have a meeting at 14:00 with someone in China while I live in the USA, there’s no conversion. It’s 14:00 everywhere. Every clock reads the same.

All it does is change what time people arbitrarily ‘Get up’, ‘Fall asleep’, ‘start school’ etc.

Sat we arbitrarily say 00:00 is what ‘midnight’ would be in Britain at the Prime Meridian.

That means nothing really changes for Britain. But in Central Time USA, 00:00 means it’s when we’re just starting dinner.

No daylight savings times anywhere. Work places can set their own work times however they want. Nobody gets confused about having to convert time to different time zones for logistics.

I’d wake up at 13:00, get breakfast, be into work at 14:00. Get home at 22:00, etc.

source

Sort:hotnew top

c0mbatbag3l@lemmy.world ⁨7⁩ ⁨months⁩ ago
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.

source
- blanketswithsmallpox@lemmy.world ⁨7⁩ ⁨months⁩ ago
  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.
  
  source
  - evranch@lemmy.ca ⁨7⁩ ⁨months⁩ ago
    
    code regarding time difference variables
    
    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.
    
    source
- evranch@lemmy.ca ⁨7⁩ ⁨months⁩ ago
  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.
  
  source
usualsuspect191@lemmy.ca ⁨7⁩ ⁨months⁩ ago
There’d still be “timezones” where the divisions on what times everyone lives by are drawn, right? Like, in this state business hours are 14:00 to 22:00, and over at this other place it’s 00:00 to 08:00. For simplicity and commerce those boundaries would likely look very much like timezones…

You’ll still need to convert to the local time like we do now in order to know what part of the day that time is, but instead of doing that conversion once, you’ll then you do it for all sorts of things and keep track of all the different times everything is in that other place too. Currently, you can look up the time it is somewhere (or add/subtract a number of hours if you’re old-school) and when you see it’s 8am, you know it’s morning there. If there are no timezones, knowing it’s 8am doesn’t actually tell you anything anymore.

source
- blanketswithsmallpox@lemmy.world ⁨7⁩ ⁨months⁩ ago
  The point is that if I say 6 p.m., you don’t know what that means for Mexico, and South Africa, and Malaysia.
  
  Any of this ‘extra step’ calculation you’re imagining is something people already do needlessly. This way those ‘time zones’ don’t matter.
  
  Train ships from NewYork at 1:00 a.m. and arrives at destination at 7:00 a.m., it then gets offloaded and trucked to Walmart at 11:00 a.m.
  
  Congrats, no having to compensate for time zone differences. A=B=C
  
  Not A=B-1 back to B+1 because you happen to ship over an arbitrary time zone line.
  
  source
  - LwL@lemmy.world ⁨7⁩ ⁨months⁩ ago
    And also, not everyone even has the same schedules. USA has common “9-5” office jobs, in germany people more commonly start at 8. So even with timezones you still need the schedule adjustment to a degree.
    
    I play online video game tournaments with players globally, one person will complain about having to play at 11 because it’s so early and would rather play at 0, someone else complains that 16 is too late and would rather play at 7. And even with many people in that community being very experienced with timezone conversion, they still occasionally mix something up.
    
    One single global time would just be better. But I also brought it up once on reddit and got pretty much the same reactions.
    
    source