justingrantjg

6 ms·

1. 1.▲
   by justingrantjg 6mo ago

   4. Why is it `Temporal.ZonedDateTime` not `Temporal.DateTime`? This is a fun story. Originally there was no `Temporal.ZonedDateTime`, and the type now called `Temporal.PlainDateTime` was called `Temporal.DateTime`. When we added a Temporal
2. 2.▲
   by justingrantjg 6mo ago

   I'm one of the volunteer open-source folks (called "proposal champions" in TC39 parlance) who designed the Temporal API. Sorry for the late reply, as you can imagine it's been a busy week for us. You raise a very importa
3. 3.▲
   by justingrantjg 1y ago

   This is a big milestone to getting Temporal shipped in Chrome (unflagged), which will have huge positive on JS developers around the world. Thank you all for your hard work to get this built and over the finish line.
4. 4.▲
   by justingrantjg 2y ago

   Yep. That said, for end users it's a fairly good story because consumer OSs have gotten very good at automatically adjusting clients' time zone based on geo-location. Just like when you fly to another country and the first thing t
5. 5.▲
   by justingrantjg 2y ago

   > https://github.com/tc39/proposal-canonical-tz - appropriately to these comments, a proposal to handle tzdb changes, built on top of JS Temporal, includes some great examples of all the ways this can happen Thanks!
6. 6.▲
   by justingrantjg 2y ago

   It's already the standard! RFC 9557 was approved late last year. https://www.rfc-editor.org/rfc/rfc9557.html
7. 7.▲
   by justingrantjg 2y ago

   There are 5 different `islamic-*` calendars (and a `persian` calendar too) supported in JS today: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... There's no geographic adjustment but
8. 8.▲
   by justingrantjg 2y ago

   Temporal includes `equals` methods on every type. String comparison sometimes works, but there are enough cases where it doesn't (especially when comparing strings that refer to the same data but were generated by different libraries s