Editing Talk:1883: Supervillain Plan
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 10: | Line 10: | ||
:To me, the position with black hat on a throne and the people opposite him seems more like a villain gloating over his plan. But the heroes this week are programmers (who else would go up against a madman who seems to be building a drone army?) - and when they hear what he's actually planning, the time zone thing becomes their biggest concern. -- [[Special:Contributions/162.158.155.110|162.158.155.110]] 09:50, 31 August 2017 (UTC) | :To me, the position with black hat on a throne and the people opposite him seems more like a villain gloating over his plan. But the heroes this week are programmers (who else would go up against a madman who seems to be building a drone army?) - and when they hear what he's actually planning, the time zone thing becomes their biggest concern. -- [[Special:Contributions/162.158.155.110|162.158.155.110]] 09:50, 31 August 2017 (UTC) | ||
− | |||
− | |||
− | |||
− | |||
Also a nice one for programmers, when governments suddenly decide to change the rules: http://www.bbc.com/news/world-europe-34631326 --[[Special:Contributions/141.101.69.177|141.101.69.177]] 20:07, 30 August 2017 (UTC) | Also a nice one for programmers, when governments suddenly decide to change the rules: http://www.bbc.com/news/world-europe-34631326 --[[Special:Contributions/141.101.69.177|141.101.69.177]] 20:07, 30 August 2017 (UTC) | ||
Line 27: | Line 23: | ||
:I'm glad the "citation needed" is back (no I didn't add it back myself), I had two "Citation needed" in that sentence but they were removed because "not funny anymore", and I did notice that it wasn't used for many pages, so I wondered if the trope was still up to date. [[Special:Contributions/141.101.88.172|141.101.88.172]] 10:11, 1 September 2017 (UTC) | :I'm glad the "citation needed" is back (no I didn't add it back myself), I had two "Citation needed" in that sentence but they were removed because "not funny anymore", and I did notice that it wasn't used for many pages, so I wondered if the trope was still up to date. [[Special:Contributions/141.101.88.172|141.101.88.172]] 10:11, 1 September 2017 (UTC) | ||
::The "Citation needed" template was used too much in the past{{Citation needed}} which some still liked and others not{{Citation needed}}. But consider, it doesn't explain anything which is the main purpose of the article.--[[User:Dgbrt|Dgbrt]] ([[User talk:Dgbrt|talk]]) 12:45, 1 September 2017 (UTC) | ::The "Citation needed" template was used too much in the past{{Citation needed}} which some still liked and others not{{Citation needed}}. But consider, it doesn't explain anything which is the main purpose of the article.--[[User:Dgbrt|Dgbrt]] ([[User talk:Dgbrt|talk]]) 12:45, 1 September 2017 (UTC) | ||
− | |||
:That was "Amsterdam time", the time on which the sun is at its highest point at noon in Amsterdam. Earlier in the 19th century, most cities held to their own time. In 1892, the railways decided to use _Greenwich_ time, even though more and more cities used Amsterdam time -- so the trains were always using a time 19m32.12 different from the rest of the country. Until 1909, as you note, when everybody had to switch to Amsterdam time, that mostly meant the railways. 08:21, 1 September 2017 (UTC) {{unsigned ip|141.101.105.228}} | :That was "Amsterdam time", the time on which the sun is at its highest point at noon in Amsterdam. Earlier in the 19th century, most cities held to their own time. In 1892, the railways decided to use _Greenwich_ time, even though more and more cities used Amsterdam time -- so the trains were always using a time 19m32.12 different from the rest of the country. Until 1909, as you note, when everybody had to switch to Amsterdam time, that mostly meant the railways. 08:21, 1 September 2017 (UTC) {{unsigned ip|141.101.105.228}} | ||
I was working on an application with multiple remote devices measuring temperatures. The units had internal clocks, but some units were set to change automatically with daylight savings time, some weren't, and some apparently had the wrong dates set for the switchover. They were also located in two different time zones. I would have loved to have them all set to UTC and handle the time zone conversion at the central facility. However, this wasn't really practical as parts of the network were already installed. However, it was good enough since the real need was to record trends and report when temperatures were above alarm levels. There is also a time standard that doesn't use leap seconds (TAI). (This is used for the GPS system.) I have heard a number of proposals that the timing standard for computer equipment use the time without leap seconds for recording events. http://tycho.usno.navy.mil/systime.html UTC is TAI with adjustments for leap seconds. Look at http://gpsworld.com/leap-second-implementation-confuses-some-receivers/ (There were other situations) Some systems had some calculations using UTC and some using TAI, and mistakes in consistency caused some major problems. [[User:BradleyRoss|BradleyRoss]] ([[User talk:BradleyRoss|talk]]) 20:46, 31 August 2017 (UTC) | I was working on an application with multiple remote devices measuring temperatures. The units had internal clocks, but some units were set to change automatically with daylight savings time, some weren't, and some apparently had the wrong dates set for the switchover. They were also located in two different time zones. I would have loved to have them all set to UTC and handle the time zone conversion at the central facility. However, this wasn't really practical as parts of the network were already installed. However, it was good enough since the real need was to record trends and report when temperatures were above alarm levels. There is also a time standard that doesn't use leap seconds (TAI). (This is used for the GPS system.) I have heard a number of proposals that the timing standard for computer equipment use the time without leap seconds for recording events. http://tycho.usno.navy.mil/systime.html UTC is TAI with adjustments for leap seconds. Look at http://gpsworld.com/leap-second-implementation-confuses-some-receivers/ (There were other situations) Some systems had some calculations using UTC and some using TAI, and mistakes in consistency caused some major problems. [[User:BradleyRoss|BradleyRoss]] ([[User talk:BradleyRoss|talk]]) 20:46, 31 August 2017 (UTC) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |