![BJ Homer on Twitter: "Javascript and Swift apparently disagree about when January 1, 1 AD was. (Both numbers in milliseconds-since-1970) JS: -62135596800000 Swift: -62135769600000 These two numbers are exactly 48 hours apart. BJ Homer on Twitter: "Javascript and Swift apparently disagree about when January 1, 1 AD was. (Both numbers in milliseconds-since-1970) JS: -62135596800000 Swift: -62135769600000 These two numbers are exactly 48 hours apart.](https://pbs.twimg.com/media/FNBzakTUcAE0Tqb.jpg)
BJ Homer on Twitter: "Javascript and Swift apparently disagree about when January 1, 1 AD was. (Both numbers in milliseconds-since-1970) JS: -62135596800000 Swift: -62135769600000 These two numbers are exactly 48 hours apart.
toISOString shouldn't return "Invalid Date" when called on a invalid moment · Issue #3632 · moment/moment · GitHub
![Instant Event not working with new Date().toISOString() · Issue #891 · elsa-workflows/elsa-core · GitHub Instant Event not working with new Date().toISOString() · Issue #891 · elsa-workflows/elsa-core · GitHub](https://user-images.githubusercontent.com/66237997/115513968-d5816100-a2ad-11eb-80d9-c0c3d29107c1.png)
Instant Event not working with new Date().toISOString() · Issue #891 · elsa-workflows/elsa-core · GitHub
![Override Date.now() based on OS time when Node returns incorrect current date - AMIS, Data Driven Blog - Oracle & Microsoft Azure Override Date.now() based on OS time when Node returns incorrect current date - AMIS, Data Driven Blog - Oracle & Microsoft Azure](https://technology.amis.nl/wp-content/uploads/2019/12/image-103.png)