1106
Daylight saving creator left the chat.... (lemmy.world)
submitted 2 years ago by to c/programmer_humor@programming.dev
243 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 years ago (1 child)

The fact that you give a preference to change something here which you give as an example for something that shouldn't be changed because it would be problematic is deeply ironic to me.

Also, again, I don't really see the problem with changing the date in the middle of the day. It's virtually the same as changing it at 00:00 or 04:00, you change the date once every 24 hours. Right now you have a situation where one persons 3rd of the month could be another persons 2nd or 4th, depending on where on the globe they are. That's not really ideal either, especially for that call scheduling example by the GP.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago (2 children)

    Don't you think it makes sense for the date to change while ~everyone is asleep?

    International light-speed communication is what we internet dwellers are used to but it's not most people's experience. Most people rarely talk to people from another continent.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] -1 points 2 years ago (1 child)

    Oh don't get me wrong, I see how it makes sense. I'm just saying that 1) it is arbitrary nonetheless and 2) it doesn't outweigh the benefits that could be gained by using a single global timezone. Incidence angle of solar radiation is hardly something most people need or even want to track beyond a certain degree (dawn, noon, dusk, midnight), and the times that would coincide with at your latitude and longitude can be easily learned.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 2 years ago (1 child)

    I guess I disagree about the benefits of a single global timezone. We already have that for technology to use - the unix timestamp. All potential benefits of a unified timezone could be (and are) gained by having software convert times to whichever timezone you need.

    Maybe I'm missing something. What do you think the benefits would be?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -2 points 2 years ago (1 child)

    We already have that for technology to use - the unix timestamp.

    A unix timestamp is an offset to a UTC date, not a timezone. But fair enough, there is UTC. It's not used by default however, except by scientists and programmers maybe.

    Maybe I’m missing something. What do you think the benefits would be?

    Removing ambiguity from casual language. Currently when you state a time you are almost always implying your local timezone applies, which might be unknown information to the recipient, especially with written sources like these comments here. With everybody using the same timezone instead you would always make an unambiguous statement about the specific time by default.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    Currently when you state a time you are almost always implying your local timezone applies, which might be unknown information to the recipient, especially with written sources like these comments here.

    In most people's everyday life that's really rare. And when it does happen it's usually clarified. In more automated contexts (e.g. a scheduled YouTube premiere) the software converts it automatically - the author inputs the date and time in their own timezone, and viewer sees the converted date and time in their own timezone.

    When it does happen it reminds us that the date and time falls on a different time of day for different participants.

    With everybody using the same timezone instead you would always make an unambiguous statement about the specific time by default.

    22:00, midday.

    Person A: "Meet me here tomorrow at 01:00"

    Person B: "Sure no problem"

    ... three hours later ...

    Person A: "Ugh, I told him to be here at 01:00, where is he?"

    ... 24 hours later ...

    Person B: "Ugh, he told me to come here at 01:00, where is he?"

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    And when it does happen it’s usually clarified. In more automated contexts (e.g. a scheduled YouTube premiere) the software converts it automatically - the author inputs the date and time in their own timezone, and viewer sees the converted date and time in their own timezone.

    My point exactly though, this is a whole lot of complexity we could just get rid of by using a single timezone, with the added benefit of that working without any automation or clarification. Next Tuesday 14:00? Same time for everybody, regardless of locality. Everyone will know what part of the solar day that is for them by habit.

    When it does happen it reminds us that the date and time falls on a different time of day for different participants.

    The complexity of coordinating different solar cycles is there either way and unavoidable. So why not use the simpler system?

    Meet me here tomorrow at 01:00

    Yes, semantic drift in these terms would be unavoidable, but I still see the long-term benefits to clarity outweighing the short-term costs in it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •