News for hackers. Stuff that matters.
Re:JavaScript's “new Date()” causing 90% of Alibaba's intern... by lightblade on Wednesday February 10, 2016 @06:03PM (#11076928)
Nope, use ISO 8601 format just like blog post suggested. It's more readable and not vulnerable to the Year 2038 problem [1].

It's also important to note that ISO 8601 format is the default format that Date object serialize to. Try it new Date().toJSON()

[1]: https://en.wikipedia.org/wiki/Year_2038_problem

Re:JavaScript's “new Date()” causing 90% of Alibaba's intern... by cbd1984 on Wednesday February 10, 2016 @09:02PM (#11077764)
Unix timestamps aren't vulnerable to the Year 2038 Problem unless you deliberately make it so they are.
Re:JavaScript's “new Date()” causing 90% of Alibaba's intern... by tdeck on Wednesday February 10, 2016 @11:20PM (#11078210)
The problem with ISO 8601 is that it isn't as simple as it looks. A lot of implementations that claim to support ISO 8601 do not parse all the different formats allowed by the standard. There are all kinds of weird edge cases like specifying a date with a year and week number that are valid.

RFC3339 defines a subset that is only the sane tinestamp format most people probably think of when they think ISO8601. It's a good alternative, although a lot of the time UNIX timestamps are honestly the most convenient option for everyone.

Source: spent a bunch of time designing a public API and thinking about this.

Re:JavaScript's “new Date()” causing 90% of Alibaba's intern... by kbart on Thursday February 11, 2016 @04:11AM (#11079098)
"It's more readable and not vulnerable to the Year 2038 problem"

What makes you use signed 32-bit Integer for Unix timestamp in this age and day? I work with embedded systems and use Unix timestamp extensively, but never have I found any serious reason to use it as int32_t.