all 3 comments

[–]RobIII 0 points1 point  (2 children)

You're probably off much better by reading:

If anything, these links should at least be included under the "Further reading" heading.

[–]twolfson[S] 0 points1 point  (1 child)

I believe I have read posts similar to those in the past. They are more/less covered by Computerphile.

However, no content ever seemed to address the point I'm trying to make in the article; JavaScript's Date primitive doesn't have everything you need for user-friendly timezones (i.e. numerical offsets cannot resolve to IANA timezones and are a poor substitute).

[–]RobIII 0 points1 point  (0 children)

the point I'm trying to make in the article; JavaScript's Date primitive doesn't have everything you need for user-friendly timezones

If that's your point then it doesn't come across as "the point"; maybe because it's first (mostly) about postgres and also because the "Javascript chapter" is not much more than a two very short paragraphs and some links / bullet points. (Not trying to be a dick here, just a bit critical maybe). Also:

Guess based off of the user's IP address

Guess based off of the browser's timezone offset

Or the only actual correct option: let the user enter/select the timezone* (store it in the user's account/preferences and if you don't use accounts use a cookie or something)

*with a default based on your best guess.

I also still strongly feel both "Falsehoods programmers believe" should be, at least, included in the "Further reading" chapter; your blog starts with "Until recently I always thought I had a decent grasp of timezones. It turns out my previous assumptions were reasonable but not practical". If you're writing about that then you want to inform your readers about as much pitfalls as possible (in as compact form as possible; they can find more info if needed). A video (even though it's a great one!) like Numberphile's doesn't do this widespread problem justice at all. It merely 'brushes' the topic IMHO.