Robin Pokorny
2025-05-28
Complexity of Clocks, Calendars, and Computers
Slide 2
2
Intro
WHAT IS THE
?
Slide 3
Intro
3
The twenty-eighth of May, two thousand and twenty-five at two o’clock in the afternoon
Slide 4
History
4
HUMAN-MADE
Slide 5
5
History
GOLDEN RATIO?
Slide 6
6
Example
28 May 2025, 2 pm
Slide 7
Example
2025-05-28T14:00:00
7
Slide 8
Example
2025-05-28T14:00:00
8
Slide 9
9
Example
20250528T140000
Slide 10
Example
2025-W22-3T14:00:00
10
Slide 11
11
Example
2025W223T140000
Slide 12
12
Example
2025-148T14:00:00 2025148T140000
Slide 13
Slide 14
Unix time: seconds or milliseconds?
1748433600000 1748433600
14
Slide 15
15
Solution for computers
WHAT TO DO
USE RFC 3339 DO NOT USE ISO
Slide 16
Example
16
2025-05-28T14:00:00+02:00 2025-05-28T12:00:00Z
Slide 17
Compare
17
Source
Slide 18
18
Solution for computers
WHAT TO DO USE RFC 9557 Internet Extended Date/Time Format (IXDTF)
USE RFC 3339 DO NOT USE ISO
Slide 19
Example
19
2025-05-28T14:00:00+02:00[Europe/Prague] 2025-05-28T12:00:00Z[Europe/Prague]
Slide 20
20
Example
2025-01-28T14:00:00+02:00[Europe/Prague] Inconsistent
Slide 21
21
Example
2035-05-28T13:00:00+01:00[Europe/Prague] Inconsistent
Slide 22
22
Temporal API
Temporal API Upcoming replacement for the Date object with full RFC 9557 (IXDTF) support and time zone arithmetic.
Slide 23
Temporal API
23
Gist
Slide 24
24
Cheat sheet
Storage and transport Y
Instant?
Y
Past?
N
RFC 3339/9557 with Z Unix timestamp RFC 9557 (Local/Z + zone)
N
RFC 9557 (Local + zone) by robinpokorny.com
Slide 25
Solution for people
Wednesday, 28 May 2025, 2 pm (Prague) Wed, 28 May, 2 pm PRG
25
Slide 26
Thanks
THINK ABOUT YOUR DATES! me@robinpokorny.com
26