• HatFullOfSky@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      Every appliance in my house (with a clock anyway) and all of our clocks (2 analog, 2 digital) require manual changing. None of them are connected to the internet, which I would think is the only way they would be able to. Do they really make “smart” analog clocks now?

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      I have four:

      • wall clock - battery powered, no date function
      • oven - not “smart,” nor do I want it to be smart
      • two cars - they’re old enough to not have smart features

      Changing them isn’t an issue, and I often don’t get to it for a few days because I rarely actually use them. But it still pisses me off way more than it should.

  • JamesStallion@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    I work for a Chinese company and my colleagues treat daylight savings time as an inexplicable religious ritual that they indulgently accommodate us ptimitives iin.

    • corvi@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      I would totally agree if Beijing didn’t force the rest of China to use their time zone, lol. Noon in Western China is nuts to experience.

    • Fox@pawb.social
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      It is a ridiculous thing, but it doesn’t strike them as odd that their own country has just one timezone despite being wider than the USA?

      • Whelks_chance@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        I’d be happy if the whole planet had the same timezone. Just adjust your personal life to global time, rather than expecting time to adjust to anyone’s work/school timetable.

        • brbposting@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          7 months ago

          I’ve read we would all compensate in ways that would essentially bring back time zones.

          Reminded me of this:

          Falsehoods programmers believe about time

          short list

          Nope I lied

          • There are always 24 hours in a day.
          • February is always 28 days long.
          • Any 24-hour period will always begin and end in the same day (or week, or month).
          • A week always begins and ends in the same month.
          • A week (or a month) always begins and ends in the same year.
          • The machine that a program runs on will always be in the GMT time zone.
          • Ok, that’s not true. But at least the time zone in which a program has to run will never change.
          • Well, surely there will never be a change to the time zone in which a program hast to run in production.
          • The system clock will always be set to the correct local time.
          • The system clock will always be set to a time that is not wildly different from the correct local time.
          • If the system clock is incorrect, it will at least always be off by a consistent number of seconds.
          • The server clock and the client clock will always be set to the same time.
          • The server clock and the client clock will always be set to around the same time.
          • Ok, but the time on the server clock and time on the client clock would never be different by a matter of decades.
          • If the server clock and the client clock are not in synch, they will at least always be out of synch by a consistent number of seconds.
          • The server clock and the client clock will use the same time zone.
          • The system clock will never be set to a time that is in the distant past or the far future.
          • Time has no beginning and no end.
          • One minute on the system clock has exactly the same duration as one minute on any other clock
          • Ok, but the duration of one minute on the system clock will be pretty close to the duration of one minute on most other clocks.
          • Fine, but the duration of one minute on the system clock would never be more than an hour.
          • The smallest unit of time is one second.
          • Ok, one millisecond.
          • It will never be necessary to set the system time to any value other than the correct local time.
          • Ok, testing might require setting the system time to a value other than the correct local time but it will never be necessary to do so in production.
          • Time stamps will always be specified in a commonly-understood format like 1339972628 or 133997262837.
          • Time stamps will always be specified in the same format.
          • Time stamps will always have the same level of precision.
          • A time stamp of sufficient precision can safely be considered unique.
          • A timestamp represents the time that an event actually occurred.
          • Human-readable dates can be specified in universally understood formats such as 05/07/11.
          • The offsets between two time zones will remain constant.
          • OK, historical oddities aside, the offsets between two time zones won’t change in the future.
          • Changes in the offsets between time zones will occur with plenty of advance notice.
          • Daylight saving time happens at the same time every year.
          • Daylight saving time happens at the same time in every time zone.
          • Daylight saving time always adjusts by an hour.
          • Months have either 28, 29, 30, or 31 days.
          • The day of the month always advances contiguously from N to either N+1 or 1, with no discontinuities.
          • There is only one calendar system in use at one time.
          • There is a leap year every year divisible by 4.
          • Non leap years will never contain a leap day.
          • It will be easy to calculate the duration of x number of hours and minutes from a particular point in time.
          • The same month has the same number of days in it everywhere!
          • Unix time is completely ignorant about anything except seconds.
          • Unix time is the number of seconds since Jan 1st 1970.
          • The day before Saturday is always Friday.
          • Contiguous timezones are no more than an hour apart. (aka we don’t need to test what happens to the avionics when you fly over the International Date Line)
          • Two timezones that differ will differ by an integer number of half hours.
          • Okay, quarter hours.
          • Okay, seconds, but it will be a consistent difference if we ignore DST.
          • If you create two date objects right beside each other, they’ll represent the same time. (a fantastic Heisenbug generator)
          • You can wait for the clock to reach exactly HH:MM:SS by sampling once a second.
          • If a process runs for n seconds and then terminates, approximately nseconds will have elapsed on the system clock at the time of termination.
          • Weeks start on Monday.
          • Days begin in the morning.
          • Holidays span an integer number of whole days.
          • The weekend consists of Saturday and Sunday.
          • It’s possible to establish a total ordering on timestamps that is useful outside your system.
          • The local time offset (from UTC) will not change during office hours.
          • Thread.sleep(1000) sleeps for 1000 milliseconds.
          • Thread.sleep(1000) sleeps for >=1000 milliseconds.
          • There are 60 seconds in every minute.
          • Timestamps always advance monotonically.
          • GMT and UTC are the same timezone.
          • Britain uses GMT.
          • Time always goes forwards.
          • The difference between the current time and one week from the current time is always 7 * 86400 seconds.
          • The difference between two timestamps is an accurate measure of the time that elapsed between them.
          • 24:12:34 is a invalid time.
          • Every integer is a theoretical possible year.
          • If you display a datetime, the displayed time has the same second part as the stored time,
          • Or the same year,
          • But at least the numerical difference between the displayed and stored year will be less than 2.
          • If you have a date in a correct YYYY-MM-DD format, the year consists of four characters.
          • If you merge two dates, by taking the month from the first and the day/year from the second, you get a valid date.
          • But it will work, if both years are leap years
          • If you take a w3c published algorithm for adding durations to dates, it will work in all cases.
          • The standard library supports negative years and years above 10000.
          • Time zones always differ by a whole hour.
          • If you convert a timestamp with millisecond precision to a date time with second precision, you can safely ignore the millisecond fractions.
          • But you can ignore the millisecond fraction, if it is less than 0.5.
          • Two-digit years should be somewhere in the range 1900-2099.
          • If you parse a date time, you can read the numbers character for character, without needing to backtrack.
          • But if you print a date time, you can write the numbers character for character, without needing to backtrack.
          • You will never have to parse a format like ---12Z or P12Y34M56DT78H90M12.345S.
          • There are only 24 time zones.
          • Time zones are always whole hours away from UTC.
          • Daylight Saving Time (DST) starts/ends on the same date everywhere.
          • DST is always an advancement by 1 hour.
          • Reading the client’s clock and comparing to UTC is a good way to determine their timezone.
          • The software stack will/won’t try to automatically adjust for timezone/DST.
          • My software is only used internally/locally, so I don’t have to worry about timezones.
          • My software stack will handle it without me needing to do anything special.
          • I can easily maintain a timezone list myself.
          • All measurements of time on a given clock will occur within the same frame of reference.
          • The fact that a date-based function works now means it will work on any date.
          • Years have 365 or 366 days.
          • Each calendar date is followed by the next in sequence, without skipping.
          • A given date and/or time unambiguously identifies a unique moment.
          • Leap years occur every 4 years.
          • You can determine the time zone from the state/province.
          • You can determine the time zone from the city/town.
          • Time passes at the same speed on top of a mountain and at the bottom of a valley.
          • One hour is as long as the next in all time systems.
          • You can calculate when leap seconds will be added.
          • The precision of the data type returned by a getCurrentTime()function is the same as the precision of that function.
          • Two subsequent calls to a getCurrentTime() function will return distinct results.
          • The second of two subsequent calls to a getCurrentTime() function will return a larger result.
          • The software will never run on a space ship that is orbiting a black hole.
          • Devices will be set to the local timezone
          • Users prefer to use the local timezone
        • MicrowavedTea@infosec.pub
          link
          fedilink
          arrow-up
          0
          ·
          7 months ago

          As a programmer I would love that. But as a person it does make more sense to go “it’s 4am in California, that person is probably sleeping” than “it’s 11am, what is the sun situation like in California rn?”

          • frank@sopuli.xyz
            link
            fedilink
            arrow-up
            0
            ·
            7 months ago

            The best counter point I’ve heard for it is that a date change would happen in the middle of the work day for half the world. That does sound tough to deal with

          • Whelks_chance@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            7 months ago

            As a programmer who works with people on both side of the pond, it often doesn’t matter what time it is there, as they’re not necessarily working standard hours anyway. They have families and errands and choose to work overnight essentially at random, so we’ve adapted to communicating asynchronously for 90% of our work.

          • taladar@sh.itjust.works
            link
            fedilink
            arrow-up
            0
            ·
            7 months ago

            Considering that there are quite a few people with unusual sleep and/or work schedules that doesn’t help nearly as much as you would think.

            • MicrowavedTea@infosec.pub
              link
              fedilink
              arrow-up
              0
              ·
              edit-2
              7 months ago

              I am one of the people with unusual sleep schedules. If you know someone well enough to know their personal timezone then you can use that regardless. It’s still useful to know the hours a country usually operates in.

            • Takumidesh@lemmy.world
              link
              fedilink
              arrow-up
              0
              ·
              7 months ago

              How about ‘the majority of businesses, offices, and people are active from 8-10 or whatever, so when my plane lands at 11:00 am in Tokyo, I can be reasonably confident that I will be able to do standard human business things’ versus, what time does Tokyo wake up?

              Also every city and even neighborhoods would end up disjointed and on their own system since even just a few miles can make a big difference on when the sun sets and rises.

              Timezones were made specifically to link people that were geographically far apart, we had a time before time zones, and people missed their trains all the time because 9pm meant something to pretty much every single person.

        • Kusimulkku@lemm.ee
          link
          fedilink
          arrow-up
          0
          ·
          edit-2
          7 months ago

          What a fucking mess that would be, nobody would have any idea what time of day anyone was talking about when they said “8 o’clock”. You’d always have to check. Now you only have to check if you want stuff to happen simultaneously.

          There’s a good reason time zones exist and why shit doesn’t work so well in China with just one. “Work starts at 8” might have a pretty different meaning to different parts over there lmao.

  • peto (he/him)@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 months ago

    The amount of times I’ve heard someone say ‘its for the farmers’ as if farmers have ever given a fuck what the clock says.

    • _bcron_@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 months ago

      I think it’s for us postal workers, so we can sleep in for an hour right before pre-Black Friday and Black Friday and Black Friday Returns and Christmas and Christmas Returns. And then when we’re finally done with Valentine’s Card season we pay it back right before Tax Return season

      • peto (he/him)@lemm.ee
        link
        fedilink
        English
        arrow-up
        0
        ·
        7 months ago

        Maybe, though I feel like this is a pretty extreme solution. It is the government though.

    • tallricefarmer@sopuli.xyz
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      Farmer here. I like daylight saving time. It saves us from getting up at 4:30am during the summer. Now if yall want to stay on daylight time year-round and not get on standard time in the winter, well that is just fine by me.

      • BlemboTheThird@lemmy.ca
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        So what if the clock says 4:30 am? It’s the same time in that you’re working the same daylight. All removing it would do for you is change the number on your clock, but for the people who work on set schedules it would change our needing to fuck with our sleep schedules twice a year

        • tallricefarmer@sopuli.xyz
          link
          fedilink
          arrow-up
          0
          ·
          7 months ago

          No, not exactly. We work on set schedules too for the most part. I have employees who have lives outside of their work. With daylight savings we start work at the same time everyday. If we’d remove it, then I have to ask them to come in an hour early during harvest. I also have a life outside my farm. I have kids who have to get to school in the morning.

          I agree that changing the clocks is bad. All I am saying is do not get rid of daylight savings time. Get rid of standard time. Let’s stay on daylight savings forever, so both farmers and non-farmers are happy.

          • sugar_in_your_tea@sh.itjust.works
            link
            fedilink
            arrow-up
            0
            ·
            7 months ago

            Does it really matter which time it is? If it says 4:30 or 5:30 on the clock, that doesn’t change anything related to the work being done, so the choice between daylight savings and standard time isn’t particularly important.

            I currently need to be at work at 9. I don’t care if the clock says 8 or 10, I just need to know when to be at work.

            I think all the complaining about which time to use is really silly, I honestly do not care which we choose, provided we eliminate changing clocks. Just pick one. Flip a coin, I honestly don’t care.

              • sugar_in_your_tea@sh.itjust.works
                link
                fedilink
                arrow-up
                0
                ·
                7 months ago

                Sure. Just pick one. I don’t care what the clock says when the sun comes up or is at its zenith, I just care that the time doesn’t change overnight.

  • TheSlad@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    Ok but hes actually got it backwards. Standard time is those four months in winter, and we use daylight savings time during the summer.

    • SkunkWorkz@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      7 months ago

      True. But depending on where on earth you are located and what time zone that location follows, DST is closer to the real Solar Time (12 o’clock is Solar noon). Like Poland follows CEST but in the eastern part of the country the Solar time is close to an hour ahead. So DST is more in sync to the actual natural time.

      • frezik@midwest.social
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        Which is why I specify tz database timezones, like “America/New York”. Pick the one that’s the city closest to you and will be on the same daylight savings time switchover dates. Then don’t worry about specifying EST or EDT or whatever.

      • Tja@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        CE(S)T reaches all the way to Finisterre in (Spanish) Galicia, well past Greenwich, which should be one hour behind, so basically at least 3 times zones. I blame Hitler.

  • Etterra@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    You laugh but there’s a thing called “farm time” that’s exactly this and has been a thing in the rural Midwest in various places. I remember visiting my grandmother in Indiana as a kid and they had it there out in the middle of fuck-off nowhere.

    • Lennny@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      M night shamallamadingdong twist - He lives in part of the reservation that does observe daylight savings.

    • Flying Squid@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      Indiana used to (mostly) ignore it, then I moved to L.A. and had to get used to it, then I moved back to Indiana a decade later and they’d started doing it. Argh!

  • Kit@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    I kind of do the same. I work 6:30am to 2:30pm for most of the year, but do 5:30am to 1:30pm during daylight savings time. It’s nice to see the sun for a little bit after work.

  • Dasus@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    Sure he does, becsuse all time-measuring devices of any sort in his house are analogue and have to be changed manually, and none them have phones which automatically corrects the time.

    So in essences they have some clocks in theirs houses which are off by an hour for four months a year. They still use the time everyone else uses, because that’s how time works.

    • Weslee@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 months ago

      You can pretty easily disable automatic daylight savings time adjustments on most devices, even my car has the option.

      • Dasus@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        Aye you can. But I just don’t believe in a whole family pretending to live in a different time than everybody else’s for 4 months.

        I do believe in lazy shits who don’t manage to change all the clocks which don’t get automatically updated, but for that person to actually put in effort to dodge the DLT? Not believable imo. You’d have to be really fucking obstinate.

        • ClassifiedPancake@discuss.tchncs.de
          link
          fedilink
          arrow-up
          0
          ·
          7 months ago

          I wouldn’t call myself a lazy shit just because I don’t care to update the clock on my fucking microwave, oven and kitchen scale. Why do all these devices have clocks anyways it does not make sense.

            • ClassifiedPancake@discuss.tchncs.de
              link
              fedilink
              arrow-up
              0
              ·
              7 months ago

              A timer works independent of whatever the current time is because it only needs to count down the passage of time. Also everyone already has multiple clocks on walls, wrists and phones.

              • Maeve@midwest.social
                link
                fedilink
                arrow-up
                0
                ·
                7 months ago

                There are lakes, ponds and puddles that exist beyond any particular ocean, if you can grasp the analogy.

                • ClassifiedPancake@discuss.tchncs.de
                  link
                  fedilink
                  arrow-up
                  0
                  ·
                  edit-2
                  7 months ago

                  I don’t know what you mean. I asked why do we need clocks on ovens. You said “to time cooking” but you can have a timer without a clock so it is still not needed and your answer is invalid.

          • Dasus@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            7 months ago

            I mean I meant like if you have clocks on the walls and such. If you have them already, why not change. But you can’t help your microwave wanting to show you the time.

            Mine doesn’t. Never had a digital one, don’t really need one, the dial ones are good enough. My oven or airfryer don’t have clocks either. My wristwatch and phone update themselves.

            I was more thinking like my dad always being too lazy to change the clocks on the walls. Didn’t mean to offend you.

  • Sam_Bass@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    research has proven time after time that the practice doesnt actually save energy or time in the modern age