Скачать или смотреть Understanding the getTime() Method in Javascript: Why Is There a One-Hour Difference?

Dive into the confusion surrounding Javascript's `getTime()` method and discover why time zones and daylight saving can lead to unexpected results.
---
This video is based on the question https://stackoverflow.com/q/70530068/ asked by the user 'Bernd' ( https://stackoverflow.com/u/1256558/ ) and on the answer https://stackoverflow.com/a/70531285/ provided by the user 'Bernd' ( https://stackoverflow.com/u/1256558/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Javascript getTime() delivers confusing results

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Introduction

Have you ever encountered the perplexing behavior of Javascript's getTime() method? If you've delved into date manipulation in Javascript, you might have realized that it can produce results that don’t always align with our expectations—especially when it comes to different time zones and daylight saving time.

Let’s dissect the situation to clarify why these discrepancies occur and how to correctly understand and work with the getTime() method.

The Core Issue

The confusion typically arises due to the way that getTime() handles dates. According to the documentation, getTime() represents time in UTC format. This leads many to believe that calling it with different instantiations of the Date object should yield consistent results, regardless of time zone.

Example Breakdown

Consider the following cases:

Using UTC:

[[See Video to Reveal this Text or Code Snippet]]

Using Local Time:

[[See Video to Reveal this Text or Code Snippet]]

If you anticipate these two outputs to be the same, you might be surprised—a full hour is missing when you run the calculations!

Questions Explored

Question A: Why Are the Results Not Equal?

The fundamental misunderstanding here lies in the expectation surrounding local and UTC times. Let's clarify that:

UTC Time: The time is consistent globally. When you call getTime() using Date.UTC(), it takes into account only UTC without any local adjustments.

Local Time: When you create a date object with local time, the interpretation changes according to your local time zone.

In the two examples above, both date representations correspond to the same physical moment in time, but the output from getTime() differs due to how local time adjusts hour offsets.

Question B: Shouldn’t There Be One Hour More?

This question surfaces from a common misconception: if you are in UTC+ 1, should your time be ahead of UTC time? Yes, but this does not affect the underlying milliseconds calculated by getTime(). Here’s the point:

When you create a date for UTC+ 1 at midnight, the actual time in UTC is six hours earlier (1 hour behind if supposed to be the same hour). Hence, the one-hour discrepancy reflects the daylight saving time adjustment at play.

Getting to the Bottom of the Confusion

The results seen from getTime() reflect the time adjusted by the respective time zones at specific moments. To sum it up:

Conceptual Clarity: Calling new Date(2021, 8, 1, 00:00).getTime() in different time zones will yield different results based on the local time representations.

Correct Use-Case Understanding: If you’re working within applications like Gantt charts, recognizing these differences is pivotal for computations and representations.

Conclusion

It’s crucial to remember that getTime() operates consistently across time zones only when considering points of time (UTC time) but not when simply observing the same local time hour. The complexity augmented by daylight saving time can lead to unexpected results.

By understanding these principles, you can better navigate the intricacies of date manipulation in Javascript and avoid common pitfalls.

Happy coding!