@BrendanEich ...why?
`new Date('2018-01-01') => Sun Dec 31 2017 19:00:00 GMT-0500 (EST)
So don't 0 pad month?
`new Date('2018-1-01')` => Mon Jan 01 2018 00:00:00 GMT-0500 (EST)
But then:
`new Date('2018-10-01')` => Sun Sep 30 2018 20:00:00 GMT-0400 (EST)
-
Show this thread
-
Replying to @thecraigmichael
What are you testing in? > new Date('2018-01-01') 2018-01-01T00:00:00.000Z is what Node.js says.
1 reply 0 retweets 3 likes -
Replying to @BrendanEich
Oh yeah! Hmmm.. I ran into this (and subsequently tested it) in Chrome.pic.twitter.com/wVgDFN7mIC
1 reply 0 retweets 1 like -
-
Replying to @BrendanEich @domenic
This is probably (?) not surprising, but using node's inspect utility, the correct date is printed in the terminal, but not in the v8 Inspector
pic.twitter.com/jiPBYWyv6t
2 replies 0 retweets 1 like -
Both those strings represent the same date. On the left: `.toTimeString()` On the right: `toISOString()`
2 replies 0 retweets 6 likes -
Thanks -- do you know why tools differ on which to call implicitly? Seems bogus.
1 reply 0 retweets 1 like
No idea, but I can see the case for either option in tooling. One is more human-readable, the other is consistent across time zones. 
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.