March 11, 2026
Time fix took its sweet time
Temporal: The 9-Year Journey to Fix Time in JavaScript
JavaScript’s new time fix has fans cheering—but they want it everywhere
TLDR: JavaScript’s new time system, Temporal, is nearing the finish line after a nine‑year push to make dates and time zones less painful. Commenters are thrilled, early testers are happy, and many say they’ll fully switch once it lands on all major servers—making everyday time handling safer and saner for everyone.
Nine years, countless meetings, and a lot of broken calendars later, JavaScript’s big time makeover—Temporal—is finally getting real, and the crowd is buzzing. Bloomberg engineer Jason Williams pulled back the curtain on how the standards committee TC39 shepherded this from idea to near-finish, and the comments came in hot with relief and impatience. “What a journey!” sums up the vibe, while early adopters brag they’ve already been living in the future with a polyfill (a temporary add‑on) and loving the modern feel. One fan called it a “pretty big” upgrade and praised a key design choice as “the MOST appreciated,” without even needing to name it—because everyone knows the old Date object’s surprises were meme material.
But the real drama? The waiting game. One commenter said the only thing holding them back is support in server platforms—translation: they’ll go all‑in once it runs everywhere. That’s the cliffhanger. Meanwhile, the community is roasting the 1995 origin story—when JavaScript borrowed Java’s Date like a last-minute tux—and celebrating a future with safer, saner time zones. There’s even a wink from a dev who got a shout-out for a “silly little quiz,” adding some wholesome hype. Verdict: Temporal is the glow‑up, and the community is ready for the rollout clock to hit zero. Read: Temporal proposal
Key Points
- •Bloomberg has actively contributed to ECMAScript standardization, partnering with Igalia and assisting proposals like Arrow Functions, Async Await, BigInt, Class Fields, Promise.allSettled, Promise.withResolvers, WeakRefs, and Source Maps.
- •Temporal began at TC39 Stage 1 in 2018 and aims to replace JavaScript’s Date with immutable types and first-class time zone and calendar support.
- •TC39’s proposal process advances from Stage 0 to Stage 4, including an intermediate Stage 2.7 for “approved in principle” pending testing and feedback.
- •JavaScript’s Date originated from a direct port of Java’s Date into early JavaScript (Mocha) in 1995, influenced by a “Make It Look Like Java” philosophy and concerns about deviating from Java.
- •Date’s shortcomings, such as mutability and inconsistent month arithmetic, have caused developer pain, motivating Temporal’s design and standardization.