Linux Kernel Spectre v2 SMT mitigations

[zx8080]

https://github.com/google/security-research/security/advisories/GHSA-mj4w-6495-6crx

[zdw]

Can we all agree that 10/03/2023 is the worst possible date format? Why is this even in use?

[__padding → zdw]

Not entirely sure what the complaint is. I know HN is skewed very US heavy - but most of the rest of the world uses D/M/Y. I for one find M/D/Y bonkers ¯\_ (ツ)_/¯

[TonyTrapp → __padding]

But you only know at this point in time that it's d/m/y because otherwise it would be a date in the future. If it said 10/03/2022, would you know if it was in October or March? This causes needless confusion when there's better alternatives for date formatting (e.g. y-m-d).

[steve1977 → zdw]

There is only one date format, ISO 8601 (YYYY-MM-DD). Everything else is just a mistake that hasn’t been corrected yet ;)

[zdw → steve1977]

RFC3339 is a more restricted subset of ISO 8601, which has the problem of allowing YYYY-Www-D and YYYY-DDD as well.

[paulryanrogers → zdw]

Legacy is a big factor. I imagine it may endure in part because you often care most about month-then-day. Year is less important when one cares about the most recent data.

IMO YYYY-MM-DD and MM-DD are best, and I try to use them everywhere I can.