> To be fair, the new opt-in "use strict" here is "switch to Temporal" Yes, but adding an entire new API that solves way more date-related problems is obviousl

> To be fair, the new opt-in "use strict" here is "switch to Temporal" Yes, but adding an entire new API that solves way more date-related problems is obviously much more difficult than fixing a very clear and well-understood bug. Temporal is only just now starting to ship, over 15 years after this bug was introduced and over 10 years since they decided to never fix the bug.