[time-nuts] leapseconds, converting between GPS time (week, second) and UTC

[Fiorenzo Cattaneo]

Yes of course you are right. NTP timebase (based on UTC with an epoch
of 1900-01-01 00:00:00, or its representation in Unix time - seconds
since 1970-01-01 00:00:00) is timezone independent.

I just wanted to make the point that in the IT world (I've worked for
Amazon, Microsoft, Twitter and now I work for another major IT
supplier) we keep spending billions of dollars to maintain really
crappy and cruddy libraries which deal with timezones, and still get
plenty of bugs every time.
Not to mention NTP issues when leapseconds are addded (the only
company which handled the last leap second correctly was google, as
they slowly slewed at the rate of 1s/hour).

So in such an abysmal situation, I would be hugely surprised to find
commercial libraries that handle UTC, UT, TAI and GPS time correctly.
It's simply not a priority.

There are a few libraries here and there that supposedly handle it
correctly, but I wouldn't count on them unless they get heavily
tested.

That was my point, sorry if I was confusing.

-- Fio Cattaneo

Universal AC, can Entropy be reversed? -- "THERE IS AS YET
INSUFFICIENT DATA FOR A MEANINGFUL ANSWER."

On Wed, Jan 16, 2019 at 3:40 AM Hal Murray <hmurray at megapathdsl.net> wrote:
>
>
> fio at cattaneo.us said:
> > we switch in and out of DST, like applications crashing because NTP applies
> > the 1 hour change in a discontinous manner, as well as iphone alarms not
> > working when the DST date is modified?).
>
> For the record, NTP works in UTC.  It doesn't know anything about time zones
> or DST.
>
>
>
> --
> These are my opinions.  I hate spam.
>
>
>