time zones

It is time. Wes and Scott attempt to blow your minds by talking about time, who’s tracking time, where does time come from, what time is it in your browser vs someone else’s server, and standards around time.

Show Notes

• 00:25 Welcome
• 00:55 Thanks to Chris Enns
• LemonProductions.ca
• Chris Enns on Twitter
• Podcast tutorials by Chris Enns on YouTube
• 03:14 What is time in the browser?
• 06:27 What are atomic clocks?
• Atomic Clocks and Cloudflare
• 08:22 Network time
• 09:35 Device time
• 11:11 Why is time so important?
• 14:35 Epoch time
• Syntax epoch convertor
• 16:58 ISO 8601 standard
• ISO 8601
• 19:20 RFC 3339
• RFC3339
• 20:35 Time zone support
• 21:59 The Temporal API

Hit us up on Socials!

Syntax: X Instagram Tiktok LinkedIn Threads

Wes: X Instagram Tiktok LinkedIn Threads

Scott: X Instagram Tiktok LinkedIn Threads

(Note: this episode originally ran in 2019.)

In the 1800s, catching your train on time was no easy feat. Every town had its own "local time," based on the position of the sun in the sky. There were 23 local times in Indiana. 38 in Michigan. Sometimes the time changed every few minutes.

This created tons of confusion, and a few train crashes. But eventually, a high school principal, a scientist, and a railroad bureaucrat did something about it. They introduced time zones in the United States. It took some doing--they had to convince all the major cities to go along with it, get over some objections that the railroads were stepping on "God's time," and figure out how to tell everyone what time it was. But they made it happen, beginning on one day in 1883, and it stuck. It's a story about how railroads created, in all kinds of ways, the world we live in today.

This episode was originally produced by Alexi Horowitz-Ghazi and edited by Jacob Goldstein. Jess Jiang is Planet Money's Acting Executive Producer.

Learn more about sponsor message choices: podcastchoices.com/adchoices

NPR Privacy Policy

In this Hasty Treat, Scott and Wes talk about Temporal Date Objects in JavaScript — a WICKED AWESOME API for working with times and dates.

Sentry - Sponsor

If you want to know what’s happening with your errors, track them with Sentry. Sentry is open-source error tracking that helps developers monitor and fix crashes in real time. Cut your time on error resolution from five hours to five minutes. It works with any language and integrates with dozens of other services. Syntax listeners can get two months for free by visiting Sentry.io and using the coupon code “tastytreat”.

Show Notes

05:11 - Temporal Now

• You can get now
  • Temporal.now.___

07:58 - Temporal Instants

• A Temporal.Instant represents a fixed point in time, without regard to calendar or location.
  • Most common way to show it is nanoseconds since unix epoch.
  • Can be formatted a few different ways.

09:59 - Calendar

• Support for different types of calendars

11:43 - Durations

• Temporal.Duration
  • There are .from and .add and subtract() methods

12:47 - Other interesting parts

• Timezones
  • Temporal.ZonedDateTime
• Temporal.YearMonth - represents a ym = new Temporal.YearMonth(2019, 6) // => 2019-06

14:51 - Polyfill (unstable)

Links

• Fixing JavaScrip Date - Maggie Pint
• https://github.com/tc39/proposal-temporal
• https://github.com/tc39/proposal-temporal/blob/main/docs/calendar.md#methods
• https://github.com/tc39/proposal-temporal/blob/main/docs/duration.md

Tweet us your tasty treats!

• Scott’s Instagram
• LevelUpTutorials Instagram
• Wes’ Instagram
• Wes’ Twitter
• Wes’ Facebook
• Scott’s Twitter
• Make sure to include @SyntaxFM in your tweets