I have a Date
summary
Explains why dates are hard: multiple calendars, irregular Earth rotation and leap seconds (UTC‑TAI gap is 37s after 2016), and fragile time zone rules that change (TZDB releases about five times a year and Lebanon once reversed a DST decision causing a one‑day mismatch). Recommends machine vs human models: use Instant/Duration for epochs and LocalDate/LocalTime/Period for human fields, prefer java.time (JSR‑310) over java.util.Date, consider kotlinx‑datetime for multiplatform, and rely on Android Project Mainline/APEX for system TZ updates when available.
AI-written summary · about
chapters (14)
- 0:00Introduction to date handling
- 1:08World calendars and time zones
- 3:43Time zone database fun facts
- 5:55UTC and Earth rotation issues
- 8:29Machine vs human time tools
- 11:23Java time history and flaws
- 13:49Joda Time and Java 8's java.time
- 15:55Java Time API explained
- 17:02Instant and Duration in java.time
- 19:07Local date and time classes
- 21:59Time zones and daylight saving
- 23:46Kotlinx datetime library
- 24:51Android time zone updates
- 26:35Choosing the right approach
