4 ms·
It's good summary of why it's a totally insane idea, and yet whenever it comes up on HN there are always a lot of commenters who are still in favour of it.
by nmeofthestate 3y ago
It's good summary of why it's a totally insane idea, and yet whenever it comes up on HN there are always a lot of commenters who are still in favour of it.
- nmeofthestate 3y agoPrevious threads. https://news.ycombinator.com/item?id=8902765 https://news.ycombinator.com/item?id=8902765 https://news.ycombinator.com/item?id=26416337 https://news.ycombinator.com/item?id=26416337
- aeternum 3y agoMany of the issues it brings up are already an issue if you work across timezones. For example "today" is already ill-defined if you're in the US and have a team in India, who's day does it refer to? It'd be much easier to just have a single "timestamp" that everyone uses then think about offsets from that.
- nmeofthestate 3y agoI work across timezones and getting rid of timezones absolutely doesn't resolve any of these problems, as the article covers.
- karmakaze 3y agoI would say the post would fare better as "Use UTC (or GPS, TAI) in certain contexts". I work remotely as does my team. Our timezones are up to 9 hours apart (maybe more with DST differences). When working on production issues UTC is best. When talking less technically it's good to add -0400 (or EDT if everyone's familiar). Even then UTC is still pretty good as most of the team's in EU/UK and can deal with that well.
- WithinReason 3y agoIt's a silly article