Mastering JavaScript Dates and Times – Fundamentals to Advanced Techniques

Time is relative across geographic locations

No universal 'now' exists; the same moment is represented as 3:00 p.m. in New York, 8:00 p.m. in London, and 4:00 a.m. the next day in Tokyo depending on civil time conventions.

Epoch time provides universal reference

JavaScript measures time in milliseconds since January 1, 1970 at 00:00:00 UTC, creating a single unambiguous number that represents the same specific moment regardless of user location.

UTC serves as the master clock

Coordinated Universal Time acts as the internet's standard reference that ignores daylight saving time and leap years, making it the essential unit for timestamp calculations.

Offsets extend beyond whole hours

Time zone differences aren't limited to full hours—India uses UTC+5:30 and Nepal uses UTC+5:45, requiring precise minute-level calculations rather than simple hour shifts.

Government rules change unpredictably

Daylight saving time can shift clocks forward or backward, but critically, governments can alter time zone rules with minimal notice, breaking applications that rely on static assumptions.

Months and leap years vary

Calendar irregularities including 28/29-day Februaries and leap years every four years introduce edge cases that commonly break date calculations in production applications.

Store in UTC, display in local time

Always persist timestamps in UTC (epoch format) to centralized databases, then convert to the user's specific local time zone only when rendering the UI for that geographic location.

Timestamps versus time zones

A timestamp is an absolute point measured from epoch in UTC without location, while a time zone is a human-defined rule set for regions to communicate time differences.

Native support limited to two zones

JavaScript's built-in Date object only supports UTC and the system's local time zone natively, forcing developers to use complex workarounds for all other time zones.

Millisecond precision for performance

JavaScript represents epoch time in milliseconds rather than seconds to support performance measurements and animation frames, requiring conversion when interfacing with Unix systems.