Formerly /u/Zagorath on the alien site.

  • 436 Posts
  • 3.32K Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle







  • Zagorath@aussie.zonetoProgrammer Humor@lemmy.mlWorst is UTC vs GMT
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    2
    ·
    1 day ago

    The difference is just another nit pick someone will find excuses to argue over

    No, it isn’t. The scientific research actually suggests that keeping DST is worse than switching back and forth. I have to admit I find that confusing, since a lot of the specific studies I’ve looked at concentrate on the effects caused by the switchover itself, but the meta-analysis doesn’t mince words:

    In summary, the scientific literature strongly argues against the switching between DST and Standard Time and even more so against adopting DST permanently.







  • Zagorath@aussie.zonetoProgrammer Humor@lemmy.mlWorst is UTC vs GMT
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    1 day ago

    Oh, I see. Yeah I suppose it is, now that you point it out. It comes from:

    • .gov: the US government
    • .nih: the US National Institutes of Health
    • .nlm: the National Library of Medicine
    • .ncbi: the National Center for Biotechnology Information

    But really, I only know it because it’s a very common host that comes up when you’re searching for published research papers. I just see “bunch of Ns .gov” and know it’s reliable.



  • Zagorath@aussie.zonetoProgrammer Humor@lemmy.mlWorst is UTC vs GMT
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    4
    ·
    1 day ago

    Yeah you’re absolutely right that it does create a tradeoff. My experience has just been that I’d usually consider it a worthwhile tradeoff. In general, the number of people who have to deal with setting meetings is lower than the number of people who attend meetings, especially when you take into account multinational companies.

    And when you’re attending a meeting, you only care about knowing what time it has been scheduled for already. It’s in scheduling that you have to work out when is going to be best for your audience, and I’m of the opinion that the distinction between “what time is this in my time zone and their time zone?” and “where does this time sit in relation to their working day?” is net neutral. With one aspect being a strict positive and the other being a net neutral (in my opinion), I think it still wins out and becomes worthwhile.


  • Zagorath@aussie.zonetoProgrammer Humor@lemmy.mlWorst is UTC vs GMT
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    2
    ·
    1 day ago

    I personally would prefer if we all used UTC. My working hours would be 23:00 to 07:00. A Brits working hours would be 09:00 to 17:00, and a New Yorker would work 13:00 to 21:00.

    But this does have its own drawbacks. Personally I just think those drawbacks, in the sorts of real-world time-related conversations I’ve had, are less than the drawbacks of dealing with varying time zones.

    But yeah, the biggest factor is daylight saving time. Doing away with it is the number one option places that use it should take, regardless of whether one advocates for abolishing time zones or not.




  • Zagorath@aussie.zonetoProgrammer Humor@lemmy.mlWorst is UTC vs GMT
    link
    fedilink
    English
    arrow-up
    33
    arrow-down
    3
    ·
    1 day ago

    You add a whole number of hours and for some a half

    Or three quarters in a few cases.

    And of course there are cases where countries spanning as many as 5 “ideal” time zones (dividing the globe into 24 equal slices) actually use a single time zone.

    And then when someone tells you the meeting is at 10:00 am, you have to figure out if they mean your time zone or theirs, and if they mean theirs, you then have to convert that to yours. Oh, but your conversion was wrong because one of you went into or out of daylight saving time between the day when you did the conversion and when the meeting took place.