31–40 of 43 posts
Earlier quoted context omitted.
Unlike Britain, Iceland does not have Daylight Saving Time, and therefore is GMT+0 throughout the year.
Am I the only programmer who is suddenly super duper envious of Iceland?
I find it somewhat interesting that when SpaceX's streams switch to views with burned-in timecode it is always in UTC. Edit: and usually in ISO8601-ish format
If you are going to design something using a time code the most obvious solution is probably to choose your own zone. When you realize that doesn't apply to anyone else, UTC is the next option. Especially because it means you don't need to deal with user configuration. As for ISO8601, that probably results from people looking for some standard to help with compatibility. If you just mean YYYY-DD-MM HH:MM that is just…
And I think SpaceX wouldn't even have the obvious option of using their own time zone. AFAIK mission control and launch are in different time zones anyway, so UTC is really the only sane option to make sure everyone refers to the same time.
It's weird that the author chooses Iceland as an example of a GMT+0 country, rather than Britain which is where Greenwich is.
This is an old article since iOS has added UTC time zone to system settings and clock app. Android still doesn’t support UTC time zone, and need to use Iceland as hack. Which depends on Iceland not changing their time zone.
I'd pick someplace reasonably close to the equator. Then there is little difference in sunrise and sunset times throughout the year, and there is pretty much no case to be made for DST on sunlight grounds.
Some good choices, if whatever you are trying to set supports any of them:
• Liberia. City of Monrovia if you have to specify by city. There's only 0:43 difference between the longest and shortest daylight periods of the year there.
• Guinea, city of Conakry.
• Togo, city of Lomé.
There are a few other countries in the general area of these three that are on UTC+0 but these three have never had DST so are probably more likely to stay that way.
Earlier quoted context omitted.
I thought UTC the same, doesn't that mean that GMT+0 is essentially wrong? I thought GMT was essentially UTC+0, and all other time zones (ignoring DST) are defined as offsets to UTC, not GMT.
Think of it as two pointers referencing the same data: Time* UTC = Time(0); Time* GMT = *UTC; *UTC == *GMT; // True UTC == GMT; // False
If, however you meant for that line to be: Time *GMT = UTC;
it would compile fine, but then your second comparison would evaluate to true, and the whole analogy be rather pointless.
Earlier quoted context omitted.
This is an old article since iOS has added UTC time zone to system settings and clock app. Android still doesn’t support UTC time zone, and need to use Iceland as hack. Which depends on Iceland not changing their time zone.
There are probably better choices than Iceland, if Android supports them. Iceland doesn't do DST now, but has in the past (1917-1918, and 1939-1968). The farther North a place is, the stronger the case for DST, so I wouldn't count on Iceland changing not their mind someday. I'd pick someplace reasonably close to the equator. Then there is little difference in sunrise and sunset times throughout the year, and there is…
I disagree. If you get to the north pole or anywhere near the Arctic Circle (where Iceland is), it can still be dark at noon in the winter and light at midnight in the summer. You can't nearly compensate for that with a mere hour change, so why bother?
Earlier quoted context omitted.
This is an old article since iOS has added UTC time zone to system settings and clock app. Android still doesn’t support UTC time zone, and need to use Iceland as hack. Which depends on Iceland not changing their time zone.
Had anyone here tried to live life with their iPhone on UTC?
Earlier quoted context omitted.
If you are going to design something using a time code the most obvious solution is probably to choose your own zone. When you realize that doesn't apply to anyone else, UTC is the next option. Especially because it means you don't need to deal with user configuration. As for ISO8601, that probably results from people looking for some standard to help with compatibility. If you just mean YYYY-DD-MM HH:MM that is just…
It’s yyyy-mm-dd not yyyy-dd-mm....
I find it somewhat interesting that when SpaceX's streams switch to views with burned-in timecode it is always in UTC. Edit: and usually in ISO8601-ish format