π Time Standards
Understanding the standards that govern time representation in computing.
π UTC (Coordinated Universal Time)
The primary time standard by which the world regulates clocks and time. UTC is the successor to Greenwich Mean Time (GMT) and is not affected by daylight saving time.
Key Points:
- β’ Always store timestamps in UTC
- β’ Convert to local time only for display
- β’ UTC does not observe daylight saving time
- β’ Leap seconds are occasionally added to UTC
β° Unix Time (POSIX Time)
The number of seconds since January 1, 1970, 00:00:00 UTC (the Unix epoch). Widely used in computing systems for timestamp storage.
Current Unix Timestamp:
Important Notes:
- β’ 32-bit systems will overflow on January 19, 2038 (Y2K38 problem)
- β’ JavaScript uses milliseconds since epoch, not seconds
- β’ Does not account for leap seconds
- β’ Always represents UTC time
πΊοΈ IANA Time Zone Database
The authoritative source for time zone information, maintained by the Internet Assigned Numbers Authority. Provides historical and current time zone rules for locations worldwide.
Examples:
- β’ America/New_York
- β’ Europe/London
- β’ Asia/Tokyo
- β’ Australia/Sydney
π ISO 8601
International standard for date and time representation. Defines formats for dates, times, durations, and time intervals.
Common Formats:
- β’ Date: 2024-03-15
- β’ Time: 14:30:00
- β’ DateTime: 2024-03-15T14:30:00Z
- β’ With timezone: 2024-03-15T14:30:00+01:00
π RFC 3339
A profile of ISO 8601 for use in Internet protocols. More restrictive than ISO 8601 but widely supported in APIs and web services.
Format:
YYYY-MM-DDTHH:MM:SS[.fraction]Β±HH:MM
π§ Coming Soon
- β’ Windows Time Zone Mappings
- β’ Leap Seconds and TAI
- β’ Calendar Systems (Gregorian, Julian, etc.)
- β’ ISO Week Date System