Message from JavaScript discussions
October 2018
— Looking at you and your weird ass APIs, Chrome
Speaking of which, trynew Date("5") in Chrome.
I haven't even been able to explain this since my roommate asked about this weird behaviour
— Happens in node as well
— One of the main reasons there’s so much bad blood between W3C and WHATWG is because Apple/MS/Google all made the problems they claimed to solve WORSE beforehand, ignoring the careful XHTML planning of W3C and opening a black hole of confusion for no good reason
— Not for me
— Chrome fails, node succeeds
— Chrome, node (tested on versions 6-10),new Date("5") is April 30th 2001
— W3C: “lets spend 10 years refining the ultimate stable DOM spec”
WHATWG members: “lets add stuff because it sounds cool!”
— Firefox, edge and chakracore: new Date("5") is Invalid Date
— Now W3C has to straight up copy WHATWG spec to stay relevant unless they want to wind up making a totally divergent spec, they are forced to pretty much fall in line to avoid more confusion
— W3C contributors are pissed off for that reason
— They got derailed for money