Comment Fix the software and not the physics (Score 1) 470
The ITU cannot fix this problem. In charge is the "International Committee for Weights and Measures" http://en.wikipedia.org/wiki/International_Committee_for_Weights_and_Measures
which is older than the ITU. The software should reflect the time defined by the committee. The whole discussion is ridiculous, you only need a table with the number of leap seconds defined and a function fixing the 24 exceptions to the unleaped time
http://en.wikipedia.org/wiki/Leap_second
If we would not have fixed it, the deviation would sum up to nearly half a minute. How want you fix that? In an effort similar to the Y2K bug problem. Painful nonsense.
If a database crashes you should fix the code starting with the underlying operating system and programming languages. By the way the definition of Time in most languages should be corrected, because f.e. http://download.oracle.com/javase/1.4.2/docs/api/java/sql/Time.html#Time(int, int, int) It is wrong that a minute can have only 60 seconds. It could also have 59 (not yet happened) or 61 seconds. If the ITU makes the change, time in GPS announced and real time will deviate. This is nonsense.
If we would not have fixed it, the deviation would sum up to nearly half a minute. How want you fix that? In an effort similar to the Y2K bug problem. Painful nonsense.
If a database crashes you should fix the code starting with the underlying operating system and programming languages. By the way the definition of Time in most languages should be corrected, because f.e. http://download.oracle.com/javase/1.4.2/docs/api/java/sql/Time.html#Time(int, int, int) It is wrong that a minute can have only 60 seconds. It could also have 59 (not yet happened) or 61 seconds. If the ITU makes the change, time in GPS announced and real time will deviate. This is nonsense.
