Post

Temporal inherits 3+ design flaws from CLDR: - (ISO) Weeks should have their own calendar system. - Gregorian lunar months (from its Easter Computus) should be available as their own calendar system. - There should be (at least) one optional level between year and month, e.g. season.

3/3/26, 7:48 am0 reposts5 likes

unicode-org.atlassian.netJira

3 Mar

This should probably be fixed by Unicode/CLDR first, ECMA/Javascript second. unicode-org.atlassian.net/browse/CLDR-...

3 Mar

Put differently, within a calendar system, each grouping of dates should be a true superset of all smaller/descendant groupings, i.e. either each month consists of a whole number of full weeks or they are part of different systems used in parallel.

3 Mar

Also, the start (and therefore end) of a date should be able to differ from midnight. It should be simple for authors to declare additional (special-purpose,custom, novel or rare) calendar systems. 10^8 days is wide enough a span for all of recorded human history, but not enough for astronomy.

Hi! Thanks for the suggestions. A calendar-like abstraction for times of day was considered (called a "time scale" or "time calendar"), but it was not included due to limited use cases. It could still be added later.

A pluggable calendar API was part of an earlier version of the proposal, but it was dropped due to complexity and limited use cases. You can read more about the reasoning and options in github.com/tc39/proposa....

Hi! I'm a champion for Temporal focusing on Intl support. 1. We shipped with minimal week-of-year support. More features can be added later. Tracking issue: github.com/js-temporal/... ...

2. Additional calendar systems such as the Christian liturgical calendar can be added later after they land in CLDR. There are multiple open CLDR issues for supporting more calendars. This is less a "design flaw" and more a resourcing issue. ...