Why did JavaScript need a new time API instead of just minor fixes to `Date`?
Show answer & explanation
Answer: Because `Date` has deep design problems, not just a few small bugs
Because `Date` only works on weekends — Wrong. `Date` can represent any day; weekends are not the issue.
Because `Date` has deep design problems, not just a few small bugs ✓ — Correct! `Date` mixes too many jobs into one mutable type: calendar dates, clock times, time zones, and exact instants. That creates footguns like zero-based months, inconsistent string parsing, silent timezone conversions, and DST surprises. Temporal separates these concepts into types like `PlainDate`, `Instant`, and `ZonedDateTime`, so JavaScript needed a new model, not just a few patches.
Because JavaScript wanted to remove time support entirely — Wrong. JavaScript still needs strong time support; Temporal is an attempt to improve it, not remove it.
More Technology questions
- Why can Cloudflare's lava-lamp camera feed improve encryption even though the cryptographic software that consumes it is deterministic?
- If an attacker learns a pseudorandom generator's seed and algorithm after watching several outputs, why can the later outputs become reconstructable?
- If a phone game shuffle and a physical noise source both look messy, what makes only one useful for security against someone who knows the code?
- At parking-lot speed, why do quiet EVs need alert sounds before tire noise helps?
- Why does the Ferrari 296 cabin sound duct take sound before exhaust treatment?
- Why do sound engineers tune engine orders instead of just making a Ferrari-like exhaust louder?