I have a Date
summary
Argues that concrete choices matter: drop java.util.Date because it’s mutable and misleading, prefer java.time or ThreeTenABP for up‑to‑date TZ rules, and consider kotlinx-datetime for multiplatform needs (still alpha). Cites TZ database updates, Project Mainline/APEX for shipping zone rules, the 2038 32‑bit epoch issue, and the current 37‑second leap‑second offset. Shows Instant/ISO output and Duration results (e.g. PT24H) and notes bundling TZ data in APKs works but OEM support remains uncertain.
AI-written summary · about
chapters (10)
- 0:00Handling dates in Android
- 6:29Date and time challenges
- 8:57Java date APIs flaws
- 11:03Modern Java time APIs
- 13:10Machine time management
- 15:39Human time management
- 18:15Time zones and DST rules
- 20:03Kotlin date time library
- 21:27Android time zone updates
- 23:13Choosing date library
