1. 11
  1.  

  2. 1

    I hate dealing with time zones, but this API actually looks reasonably sensible. Especially solving the amazingly frustrating task of parsing the accepted JS date strings.

    That said it seems to make it much more complicated to just calculate wallclock time and I feel that’s a lot of what people use the Date object for.

    1. 1

      Nice, just yesterday I had to deal with some issues caused by the Date object and it’s lack of support for representing a timezone other than the local one, which ultimately I had to solve by using Luxon. I’d completely forgotten about this proposal.

      The Date object is of the sharp edges of JS I’ve actually had issues with in the past, as opposed to the operator coercions rules that were the subject of that quiz I saw yesterday, so I’m really glad there’s a new API on its way.