The time relativity principle
summary
Shows that epoch and offsets are concrete sources of bugs: some databases use 30 Dec 1899 as zero, .NET uses year 1 and Oracle 2004, so parsing an XML timetable into java.time.Instant via GregorianCalendar yields wrong instants and surprising offsets (historical zones like UTC+1:24 or DST shifts change results). Notes Samoa’s 29 Dec 2011 jump across the dateline and recommends domain models: use minutes-since-midnight or Duration for timetables instead of a naïve LocalDateTime.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:45Time table
- 1:17Time zero
- 2:20Epoch
- 3:02Java
- 5:44Timezone changes
- 6:32Some More Island
- 7:59American Samoa
- 8:28Wall time
- 9:11Converting to string
- 10:50Timetable example
- 14:00Conclusion
related talks
39mThe Pearls and Pitfalls of DateTime
42mWHY A WHOLE COUNTRY SKIPPED A DAY: FUN WITH TIMEZONES AND LOCALES
52mMake a Date with Java
15mJava 8 Date&Time benefits
54mThreeTen (JSR 310) the new Date and Time API in Java 8
27mIt's Only a Matter of Date
16m8 Java quirks in 16 minutes
01h 00mon Java - Historical Oddities & Persistent Itches
