• 0 Posts
  • 22 Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle
  • Not very convenient if a date change happens during your typical workday and that your meeting is from Monday 23:00 o’clock until Tuesday 1:00 o’clock. I mean, sure, we could deal with it, but locally it only adds new complexity.

    Sure, you could talk with anyone in the world and agree on a time without misunderstandings, but as soon as you want to know if people in the other country are even awake at that time, or if it’s during business hours, you need to do the same calculations as before and need to look up how many hours the schedule is shifted in that country, similar to before.

    My Anki deck (flashcards app) would like to know when it’s the next day. It now uses a standard (configurable) value worldwide (4:00 o’clock, to allow for late nights). If we used UTC everywhere, a standard value wouldn’t make any sense, and you would have to know the local offset, and change it when you are traveling.

    Taking about traveling: instead of just changing the time zone on your devices and be done with it, you need to look up what time you should go to sleep and wake up and at what time the stores open to fit the local schedule and none of the hours that you’re used to would make any sense. Let’s have dinner at 19:00 o’clock. No, wait, that’s in the early morning here.

    We already have UTC as a standard reference, and we don’t need to adopt it for local time, as long as the offset is clear when communicating across borders. Digital calendars already take time zones into account, so when I’m inviting people from overseas, they know at what time in their local timezone the meeting starts.

    The issue is not the time zones, but the fact that we live on a sphere revolving around a star and that our biological system likes to be awake when it’s light outside.






  • Some features/plugins can be quite taxing on the system and in extreme cases it can slow the editor down to the point of being unusable. I’m a happy Neovim user with a LazyVim setup, but I experience this extreme slowdown for some JSON files and I haven’t looked into it yet to see what causes it.

    You can let your editor do the same compute intensive or memory hogging things that a GUI editor does. The fact that it runs in your terminal doesn’t make it lightweight by definition.


  • oktoberpaard@feddit.nltoADHD@lemmy.worldHeya guys.
    link
    fedilink
    English
    arrow-up
    2
    ·
    6 months ago

    A general remark rather than an answer to your question: in general, more than not equal better with vitamins, and too much vitamin B6 can lead to nerve problems. I would only supplement when you have a good reason to believe that you’re deficient. If you insist, at least try to stick to normal doses.





  • Imagine a camera with only one column of pixels, so a resolution of 1x3000, for example. You point it in a fixed direction and you keep firing extremely fast. Eventually you’ve photographed everything that has passed the camera. Paste the pixels together from right to left, and you’ve got something resembling a normal photograph, but with some distortions due to the time difference between the photos. For example, if someone put their foot on the ground in front of the camera, it will be stationary between photos and appear smeared out in the final result. Since every column of pictures is made at the exact same location, you can determine that the person on the right has finished first and the person on the left last. They apparently measure this at the level of the torso (the red lines).







  • It’s Markdown syntax. You can actually format it nicely in a code block:

    bool isEven( long long x ) {
      if ( x < 0 ) x = -x;
      if ( x == 1 )
        return false;
      if ( x == 2 )
        return true;
      return isEven( x - 2 );
    }
    

    You do that by adding ``` above and below it. To force single line breaks, you can terminate your sentences with two spaces, or a backslash.



  • But then when you’re talking about 10:00 hours without specifying anything else, it actually means something completely different in the local context, apart from it being the exact same time globally. It doesn’t tell you whether it’s night or day at the other persons location. Your default point of reference in that system is the world, while even today, time is mostly used in a local context for most people. When I’m talking to someone abroad and I say “my cat woke me up at 5:00 in the morning”, I expect the other person to get the meaning of that, because the other person understands my local context.

    When planning meetings you’d have to now the offset either way, because I’m not going to meet at idiotic times if there is an overlap in working hours between the two countries, which is something that you’d have to look up regardless of the time system. And if I send out a digital invite to someone abroad, the time zone information is already encoded inside it, and it shows up correctly in the other person’s agenda without the need to use a global time. In that sense UTC already is the global time and the local context is already an offset to that in the current system. We just don’t use UTC in our daily language.

    But if it helps: I do agree that in an alternative universe the time system could’ve worked like that and it would have functioned. I just don’t see it as a better alternative. It’s the same complexity repackaged and with its own unique downsides.


  • But with such a system in place, what are we actually solving? If we’re agreeing on offsets (which would happen in a sane world), we’re just moving the information from one place to another. In both systems there is a concept of time zones, but it’s just the notation that’s different, which adds a whole new bunch of stuff to adapt to that’s goes very much against what is ingrained into society, without offering much in return. It’s basically saying “it’s 10:00 UTC, but I’m living in EST, so the local offset is -5 hours (most people are still asleep here)” [1]. Apart from the fact that you can already use that right now (add ISO 8601 notation to the mix while you’re at it), it doesn’t really change the complexity of having time zones, you just convey it differently.

    Literally the only benefit that I can come up with is that you can leave out the offset indicator (time zone) and still guarantee to be there at the agreed time. Right now you’d have to deduct the time zone from the context, which is not always possible. That doesn’t outweigh the host of new issues that we’d have to adapt to or work around in my opinion.

    [1] In practice we would probably call that 10:00 EST, which would be 10:00 UTC, but indicate the local offset.