Home

Future Direction for Cross-Platform Date-time Library wrt Temporal

How long until Temporal a) done, b) requires polyfill?

API we want

I think having an API that mirrors another, such as java.time has value because:

• No need to document it
• Tests - copy existing test suites?

Other goals

• dependency free or fully cljs minifiable

java.time on jvm and Temporal on js

Not the same, but similar: http://widdindustries.com/ecma-temporal-vs-java-time/

options

• keep js-joda

good: api is already done. little mismatch on platforms bad: code not readily minifiable - will they use Temporal underneath?

• just use Temporal

cljs just has methods we implement aim to implement everything, but start with a subset? need to have more tests etc how will ppl include polyfill? foreign-lib aargh! :0

• just use Temporal... but have a more temporal focused api

ie not a java.time mirror, but Temporal mirror - and use java.time on jvm see https://github.com/henryw374/Temporal.jvm

Lots of options. would all be significant effort.

I'm unlikely to even start in earnest without funding.