This. Sadly I don't think it's politically easy for the committee to admit this.https://twitter.com/oshepherd/status/660807589480001536 …
@oshepherd @laurentbercot @whitequark @eevee There are other important things too, like ability to interpret times without ext. data.
-
-
@RichFelker@laurentbercot@whitequark@eevee This involves keeping times in their *entry* format. It is the *only* way which works -
@RichFelker@laurentbercot@whitequark@eevee Standardizing on any UTx fails for this because timezones do change -
@oshepherd@laurentbercot@whitequark@eevee Keeping them in UT1 works just as well. Many times (e.g. server logs) do not care about TZ's. -
@RichFelker@laurentbercot@whitequark@eevee For times in the past we have the tables. Problem is for times in the future. -
@RichFelker@laurentbercot@whitequark@eevee (esp. considering that 99% time sources are TAI/UTC, keeping clock in UT1 requires tables) -
@oshepherd@laurentbercot@whitequark@eevee Twitter is not the right medium for this discussion. And we're not going to agree anyway.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.