And if you _do_ want to assign blame, it's fine to put it on us. I did as much in the talk: "Just as we at Google did not at first understand the significance

And if you _do_ want to assign blame, it's fine to put it on us. I did as much in the talk: "Just as we at Google did not at first understand the significance of handling leap second time resets correctly, we did not effectively convey to the broader Go community the significance of handling gradual code migration and repair during large-scale changes." Our fault, both times.