[154377] in North American Network Operators' Group
Re: F-ckin Leap Seconds, how do they work?
daemon@ATHENA.MIT.EDU (Joel jaeggli)
Tue Jul 3 11:20:20 2012
Date: Tue, 03 Jul 2012 08:18:47 -0700
From: Joel jaeggli <joelja@bogus.com>
To: valdis.kletnieks@vt.edu
In-Reply-To: <217021.1341327089@turing-police.cc.vt.edu>
Cc: nanog@nanog.org, "Wolfgang S. Rupprecht" <wolfgang.rupprecht@gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 7/3/12 07:51 , valdis.kletnieks@vt.edu wrote:
> On Tue, 03 Jul 2012 07:02:33 -0700, Joel jaeggli said:
>
>> Apps are buggy sounds like a really poor excuse for doing so.
>
> When the published API has been "the system clock is in UTC" for some 3
> decades, I hardly think it's acceptable to call apps "buggy" for assuming that
> the system clock is in fact using UTC and breaking if you switch it to
> something that's not UTC. And the new time *has* to have different semantics
> than UTC, because if it doesn't then what's the point of changing it?
right you and I agree, proposing to switch off UTC becuase of buggy
applications is a rather bad premise.
software runs into trouble with the handling of leap years. yet few
people (apart from perhaps the orthdox church is proposing to throw off
the julian and gregorian calender reforms.
