The Past, Present, and Future of JavaScript Date and Time APIs
summary
Shows why the built‑in Date is broken with concrete demos: an HTML5 date input parses to the wrong day because date-only treated as UTC, adding one month yields March 2 in some time zones because of overflow plus UTC conversion, and start‑of‑day isn’t always midnight across DST. Compares Moment (mutable, widely used), date‑fns (small modular functions), and js‑joda (immutable, Joda model), cites Stage 1 ECMAScript work, and proposes fixes like zero-based months becoming 1‑based and an immutable mutable API replacement for scheduling correctness.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:56What is a Date object anyway?
- 2:06Demo
- 6:38In the beginning...
- 8:05What is wrong with the Date object?
- 10:22Ok, one more for the lulz...
- 11:47The Rise of the Date Time Libraries
- 16:18js-joda
- 19:40Examples
related talks
03mFixing JavaScript Date
19mProgramming in the 4th Dimension - Making Time Make Sense
16mA 50-year accident: how JavaScript got Date, and why Temporal exists
29mTemporal: Keep Time on Your Side
45mTemporal Collapse in JS
58mIt's Time to Talk About Time
46mFrom Roman Emperors to the Temporal API: Conquering Dates and Times in JS
41mCross Platform DateTime Awesomeness