qsort a day ago

To be fair it's exactly the type of stuff I'd be glad if I never have to think about again.

thoughtpalette 20 hours ago

Built a scheduler with pretty much all my moment/moment-tz questions answered through ChatGPT. One of the things it excels at, crawling long lived API documentation, answers, etc.

themafia 21 hours ago

The Date API is fine and relatively normalized. Once you understand it it's very easy to work with. It's biggest problem is that it simply does not support timezones, which is the main reason to use Temporal.

  • [removed] 20 hours ago
    [deleted]
  • LtdJorge 20 hours ago

    The Date API is horrible

    • themafia 17 hours ago

      Yea, that's understood to be the opinion, blandly repeating it adds little to the discussion.

      It's simple. In it's simplicity it left many features on the floor. I just can't connect with the idea that someone would need to constantly be on MDN in order to work with it. It's not so horrible that it defies logic.

      • acdha 15 hours ago

        It’s not simple, though. Simple would be something like an object wrapping YYYY-MM-DD, like a COBOL programmer in the 1950s would’ve used. Instead, people have made thousands of variations of bugs around the complexity even basic usage forces you to internalize like the month number being zero-based while the year is 1900-based but the day of the month is 1-based following standard usage.

  • winstonp 21 hours ago

    yep. i had a hell of a time building a scheduling system for a business that worked across timezones with the date API