15.1 The Architecture of Time: The Unix Epoch

In JavaScript, time is fundamentally represented as a single 64-bit floating point integer representing the number of milliseconds that have elapsed since midnight on January 1, 1970, UTC (Universal Coordinated Time). This benchmark moment is globally known as the Unix Epoch.

// High performance timestamp generation (zero memory allocation)
const startTimestamp = Date.now();
console.log(startTimestamp); // e.g. 1790620980123

// Object instance timestamp
const now = new Date();
console.log(now.getTime());   // Exact same millisecond counter
console.log(Number(now));     // Implicit conversion invokes valueOf() returning ms

15.2 The 4 Date Constructors & The Month Index Trap

The Date constructor has four distinct invocation signatures. Depending on the arguments supplied, the JavaScript runtime parses your input as an instant, a string, or component pieces:

// 1. Current moment
const current = new Date();

// 2. From millisecond offset
const epoch = new Date(0); 
console.log(epoch.toUTCString()); // "Thu, 01 Jan 1970 00:00:00 GMT"

// 3. From ISO 8601 string (always use 'Z' for UTC or explicit timezone offsets)
const launch = new Date("2026-09-30T14:30:00Z");

// 4. Component constructor: (year, monthIndex, day, hours, minutes, seconds)
// Note: September is month index 8 (9 - 1)
const workshop = new Date(2026, 8, 30, 14, 30, 0);
console.log(workshop.toDateString()); // Wed Sep 30 2026

15.3 Getters & Setters: Local vs. UTC Time

Every Date instance provides two parallel sets of getter and setter methods: one based on the user's local operating system timezone, and the other based on Universal Coordinated Time (UTC).

const meeting = new Date("2026-10-15T10:00:00Z");

// Reading both time frames
console.log("UTC Hour:", meeting.getUTCHours());      // 10
console.log("Local Hour:", meeting.getHours());       // e.g. 15 (if local is UTC+5:30)

// Mutating with Setters
meeting.setDate(meeting.getDate() + 7);               // Move forward by 1 week
meeting.setHours(14, 30, 0);                          // Reschedule local time to 2:30 PM

console.log("Updated meeting:", meeting.toISOString());

15.4 Date Formatting & Modern Intl.DateTimeFormat

Formatting dates manually using string concatenation is error-prone and ignores international linguistic standards. JavaScript provides built-in serializing methods and the powerful Intl.DateTimeFormat API:

const eventDate = new Date("2026-11-26T18:45:00Z");

// Format for Tokyo in Japanese
const tokyoFormatter = new Intl.DateTimeFormat("ja-JP", {
  timeZone: "Asia/Tokyo",
  dateStyle: "full",
  timeStyle: "short"
});
console.log(tokyoFormatter.format(eventDate)); 
// "2026年11月27日金曜日 3:45"

// Format for London in British English
const londonFormatter = new Intl.DateTimeFormat("en-GB", {
  timeZone: "Europe/London",
  weekday: "long",
  year: "numeric",
  month: "long",
  day: "numeric",
  hour: "2-digit",
  minute: "2-digit"
});
console.log(londonFormatter.format(eventDate));
// "Thursday, 26 November 2026 at 18:45"

15.5 Date Arithmetic & Elapsed Time Calculations

Because JavaScript converts Date objects to numeric milliseconds in mathematical expressions, calculating the difference between two timestamps is as simple as subtraction:

const releaseDate = new Date("2026-12-31T00:00:00Z");
const currentDate = new Date("2026-09-30T00:00:00Z");

// Subtracting yields millisecond difference
const diffMs = releaseDate - currentDate;

// Time Unit Conversion Constants
const MS_PER_SECOND = 1000;
const MS_PER_MINUTE = 60 * MS_PER_SECOND;
const MS_PER_HOUR   = 60 * MS_PER_MINUTE;
const MS_PER_DAY    = 24 * MS_PER_HOUR;

const daysRemaining = Math.floor(diffMs / MS_PER_DAY);
console.log(`Days until launch: ${daysRemaining} days`); // 92 days

// Checking for Leap Years
function isLeapYear(year) {
  return (year % 4 === 0 && year % 100 !== 0) || (year % 400 === 0);
}
console.log("Is 2026 a leap year?", isLeapYear(2026)); // false
console.log("Is 2028 a leap year?", isLeapYear(2028)); // true

15.6 Legacy Gotchas, Flaws & The Temporal Bridge

The JavaScript Date API was originally written by Brendan Eich in 1995 in under 10 days, largely porting Java's flawed java.util.Date implementation. As a result, it suffers from several architectural flaws:

15.7 Interactive Practice Labs

15.8 Hands-on Challenge & Chapter Quiz

function addBusinessDays(startDate, numDays) {
  // Clone to avoid mutating caller date!
  const result = new Date(startDate);
  let added = 0;

  while (added < numDays) {
    result.setDate(result.getDate() + 1);
    const dayOfWeek = result.getDay(); // 0 is Sunday, 6 is Saturday
    if (dayOfWeek !== 0 && dayOfWeek !== 6) {
      added++;
    }
  }
  return result;
}

// Verification:
const friday = new Date("2026-10-09T09:00:00Z"); // Friday
const delivery = addBusinessDays(friday, 3);      // Should land on Wednesday (skipping Sat & Sun)
console.log(delivery.toDateString()); // "Wed Oct 14 2026"