• aubertlone@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    10 months ago

    I mean wouldn’t any sensible developer just use one of the many npm packages that do count down from UTC?

    Which would also be using JavaScript?

    Sorry I don’t mean to quibble it’s just that imo JavaScript has nothing to do with this faulty countdown, it has to do with the developer overlooking edge cases.

    • el_abuelo@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 months ago

      So because they messed up, they’re not a sensible developer? Jeez…I sure wouldn’t like to work with you.

      Mistakes are part of life, especially when your job is solving problems, and thus you can be both a sensible developer and still make mistakes.

      If you’re not making mistakes, you’re not trying hard enough.

      • aubertlone@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 months ago

        You make it sound like I verbally abuse people for bad code.

        It’s famously difficult to implement your own time-based systems that also deal with timezones.

        Ya know, I’m fairly certain I wouldn’t want to work with someone like you either, who seems to jump to conclusions based on an off-hand comment I made that wasn’t meant to be particularly cynical.

        My main point of the previous comment is that it has nothing to do with JAVASCRIPT, just the developer on the other end. Drawn whatever conclusions you want from that assertion

    • 4am@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      Wouldn’t those also reflect an error in the local system clock if it was not set correctly?