Re: [LEAPSECS] Bloomberg announced its smear

On Sun, Sep 25, 2016 at 10:53 PM, Poul-Henning Kamp wrote: > > In message <1474862124.16870.7.ca...@systemeyescomputerstore.com>, John > Sauter writes: > >>Google says in the blog that they did the smearing to avoid the need to >>review all of their time-sensitive

Re: [LEAPSECS] Bloomberg announced its smear

In message <1474862124.16870.7.ca...@systemeyescomputerstore.com>, John Sauter writes: >Google says in the blog that they did the smearing to avoid the need to >review all of their time-sensitive code. Those of us who love leap >seconds need to spend the next 10 years doing that code

Re: [LEAPSECS] Bloomberg announced its smear

On Sun, 2016-09-25 at 19:08 -0700, Christopher Hoover wrote: > Steve, > > Google smears, too[1].  Smearing is a good engineering solution for > datacenter-scale computing and planet-wide databases [2]. > > Disclosure: I"m at Google. > > -christopher. > 73 de AI6KG > > [1]

Re: [LEAPSECS] Bloomberg announced its smear

Brooks, > The Microsoft Azure approach of moving the leap second to local midnight has > been discussed. > I suppose you mean at LEAPSECS? If so I've missed that and be interested in > the reference. > I'd be interested in any other discussions of it as well. There are several dozen posts in

Re: [LEAPSECS] Bloomberg announced its smear

Hi Gerry, On 2016-09-25 07:58 AM, GERRY ASHTON wrote: The Microsoft Azure approach of moving the leap second to local midnight has been discussed. I suppose you mean at LEAPSECS? If so I've missed that and be interested in the reference. I'd be interested in any other discussions of it as

Re: [LEAPSECS] Bloomberg announced its smear

The Microsoft Azure approach of moving the leap second to local midnight has been discussed. I don't know enough about Azure to say if it is acceptable in that context, but as a general approach, I object to midnight. National authorities in the US and Canada have decided the hour shift for