Joseph Gwinn writes:
> On Sun, 30 Oct 2022 07:08:25 +, Poul-Henning Kamp wrote:
> The other ting to keep in mind is the immense existing codebase of
> unix kernels et al, not to mention application code depending on
> those kernels.
This is the mistake we IT-people keep doing
On Sun, 30 Oct 2022 07:08:25 +, Poul-Henning Kamp wrote:
>
> Warner Losh writes:
>
>> The problem is time_t can't encode a leap second uniquely, but leap seconds
>> had been a thing for ~20 years when the first POSIX standards came out. It
>> was more of a willful choice to disregard
Warner Losh writes:
> The problem is time_t can't encode a leap second uniquely, but leap seconds
> had been a thing for ~20 years when the first POSIX standards came out. It
> was more of a willful choice to disregard them entirely as a simplification
> than lack of clairvoyance.
I
