3 ms·

Using gray to indicate no change makes the second map practically impossible to interpret.

by tedunangst 8y ago

mimixco 8y ago
The coloring is bad, but I think grey means "don't know yet." See Texas.
- tedunangst 8y ago
  Ugh, yeah, just saw that. That's even worse?
  - mimixco 8y ago
    Airline scheduling will be as depressing as dentistry, lol.
deathanatos 8y ago
I attempted to fill in the areas not making any changes with their original zone: https://i.imgur.com/ZJZwc46.png https://i.imgur.com/ZJZwc46.png (I also made Eastern hues of purple, to clearly show they're separate. Same w/ HI/AK.) Note El Paso becomes an isolated area of what was once America/Denver (Mountain Time), but would probably become America/El_Paso. I have no idea what is going on in Oklahoma in this map, and I didn't bother to change it. I honestly can't imagine that this would last very long; the remnants of ye olde America/Chicago (which is gone, in the new) would probably join America/Salt_Lake? (at which point it becomes America/Houston?) if you're SD/NE/TX/LA. If you're KY/WI, I'd say join America/New_York and let IL/IN feel like timezone weirdos, except IN is probably used to it[1]. America/Lewiston should just rock its new place of power. Seriously people, this is why we can't have nice things. DST was a decent compromise. I for one also don't want to do DST time year round, as one will basically not see sunrise in the winter. Noon should be at noon, modulo reasonable inaccuracies due to the need to have timezones, but this being essentially a zone off bugs the purist in me. But I also kinda like leap seconds, so I'm probably a weirdo. [1]: https://en.wikipedia.org/wiki/Time_in_Indiana https://en.wikipedia.org/wiki/Time_in_Indiana
- majewsky 8y ago
  One nitpick: tzdata timezones can never join. They can only split. If a place were to join another place's timezone, it would break the representation of historic timestamps.

Using gray to indicate no change makes the second map practically impossible to interpret.

mimixco 8y ago

The coloring is bad, but I think grey means "don't know yet." See Texas.

tedunangst 8y ago
Ugh, yeah, just saw that. That's even worse?
- mimixco 8y ago
  Airline scheduling will be as depressing as dentistry, lol.

deathanatos 8y ago

I attempted to fill in the areas not making any changes with their original zone: https://i.imgur.com/ZJZwc46.png https://i.imgur.com/ZJZwc46.png (I also made Eastern hues of purple, to clearly show they're separate. Same w/ HI/AK.) Note El Paso becomes an isolated area of what was once America/Denver (Mountain Time), but would probably become America/El_Paso. I have no idea what is going on in Oklahoma in this map, and I didn't bother to change it. I honestly can't imagine that this would last very long; the remnants of ye olde America/Chicago (which is gone, in the new) would probably join America/Salt_Lake? (at which point it becomes America/Houston?) if you're SD/NE/TX/LA. If you're KY/WI, I'd say join America/New_York and let IL/IN feel like timezone weirdos, except IN is probably used to it[1]. America/Lewiston should just rock its new place of power. Seriously people, this is why we can't have nice things. DST was a decent compromise. I for one also don't want to do DST time year round, as one will basically not see sunrise in the winter. Noon should be at noon, modulo reasonable inaccuracies due to the need to have timezones, but this being essentially a zone off bugs the purist in me. But I also kinda like leap seconds, so I'm probably a weirdo. [1]: https://en.wikipedia.org/wiki/Time_in_Indiana https://en.wikipedia.org/wiki/Time_in_Indiana

majewsky 8y ago
One nitpick: tzdata timezones can never join. They can only split. If a place were to join another place's timezone, it would break the representation of historic timestamps.