4 ms·

Would have been interesting to connect back to Java's own journey to improve its time APIs, with Joda-Time leading into JSR 310, released with Java 8 in 2014. I

by plucas 7mo ago

Would have been interesting to connect back to Java's own journey to improve its time APIs, with Joda-Time leading into JSR 310, released with Java 8 in 2014. Immutable representations, instants, proper timezone support etc. Given that the article refers to the "radical proposal" to bring these features to JavaScript came in 2018, surely Java's own solutions had some influence?

apaprocki 7mo ago
I would characterize it more as Joda likely informed Moment.js, which better informed TC39 because it was within the JavaScript ecosystem. As we discussed in plenary today when achieving consensus, every programming language that implements or revamps its date time primitives has the benefit of all the prior art that exists at that instant. TC39 always casts a wide net to canvas what other ecosystems do, but isn't beholden to follow in their footsteps and achieves consensus on what is best for JavaScript. So my view is this more represents what the committee believes is the most complete implementation of such an API that an assembled group of JavaScript experts could design over 9 years and finalize in 2026.
- MBCook 7mo ago
  Well said. As a Java programmer who hasn’t touched Temporal yet in JS it is extremely similar to the new Java types like… ZonedDateTime. It’s not identical. The names of the “Plain” objects make a bit more sense to me than the “Local” names Java chose. But overall easy to use and a fantastic improvement. I can’t wait to get to use it.
mrkeen 7mo ago
Yep, JavaScript got the bad version from Java too! https://news.ycombinator.com/item?id=42816135 https://news.ycombinator.com/item?id=42816135
mexicocitinluez 7mo ago
I'm in the C# world and can attribute most of my understanding about dates and times to Noda (the .NET version of Joda). Shout out to Jon Skeet for maintaining it.

by plucas 7mo ago

apaprocki 7mo ago

I would characterize it more as Joda likely informed Moment.js, which better informed TC39 because it was within the JavaScript ecosystem. As we discussed in plenary today when achieving consensus, every programming language that implements or revamps its date time primitives has the benefit of all the prior art that exists at that instant. TC39 always casts a wide net to canvas what other ecosystems do, but isn't beholden to follow in their footsteps and achieves consensus on what is best for JavaScript. So my view is this more represents what the committee believes is the most complete implementation of such an API that an assembled group of JavaScript experts could design over 9 years and finalize in 2026.

MBCook 7mo ago
Well said. As a Java programmer who hasn’t touched Temporal yet in JS it is extremely similar to the new Java types like… ZonedDateTime. It’s not identical. The names of the “Plain” objects make a bit more sense to me than the “Local” names Java chose. But overall easy to use and a fantastic improvement. I can’t wait to get to use it.

mrkeen 7mo ago

Yep, JavaScript got the bad version from Java too! https://news.ycombinator.com/item?id=42816135 https://news.ycombinator.com/item?id=42816135

mexicocitinluez 7mo ago

I'm in the C# world and can attribute most of my understanding about dates and times to Noda (the .NET version of Joda). Shout out to Jon Skeet for maintaining it.