You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current timezone mechanism afforded is occasionally reparably ambiguous.
With respect to that the problem is genuinely difficult, based on that the timezone tables vary over time, and the operating system generally does not afford to an application its own tables, making the job of verifying its worldview problematic, and with an appreciation for that Unix Time Solves Nearly All Things™, a few problems remain which need system support for appropriate resolution.
However, there are times at which I need to be able to compute a time on a different date in the local timezone, or other various tomfoolery. This isn't actually safely possible. Timezones switch on different dates, or by different distances, meaning the same computed delta could meaningfully refer to several incompatible timezones.
In my opinion, this can be repaired through simple extension. My steps to repair the timezone API would include:
What is the current local timezone
With daylight savings
Without
Are we currently in daylight savings
When does that next change
When did that last change
Will we be in daylight savings at unixtime X
What is the local current GMT delta
What was the local GMT delta at unixtime X
It would possibly be equally/more useful to be able to create Date objects in specific timezones. At that point, merely adding the "is this datetime in DST" to the existing Date API would cover all of the above steps.
The text was updated successfully, but these errors were encountered:
The current timezone mechanism afforded is occasionally reparably ambiguous.
With respect to that the problem is genuinely difficult, based on that the timezone tables vary over time, and the operating system generally does not afford to an application its own tables, making the job of verifying its worldview problematic, and with an appreciation for that Unix Time Solves Nearly All Things™, a few problems remain which need system support for appropriate resolution.
However, there are times at which I need to be able to compute a time on a different date in the local timezone, or other various tomfoolery. This isn't actually safely possible. Timezones switch on different dates, or by different distances, meaning the same computed delta could meaningfully refer to several incompatible timezones.
In my opinion, this can be repaired through simple extension. My steps to repair the timezone API would include:
It would possibly be equally/more useful to be able to create Date objects in specific timezones. At that point, merely adding the "is this datetime in DST" to the existing Date API would cover all of the above steps.
The text was updated successfully, but these errors were encountered: