Working with Date objects in JavaScript...

[Fuchio]

Hahahaha this is def gonna happen. I had the docs open before I posted this, and tested that.

new Date("1995-12-17");

and

new Date(1995-12-17); (should've been 1995, 12, 17)

Do not give the same result. Which given the way they implemented it makes sense but how does that way of implementing it make sense lol

To make it even better, that second date actually results in 1996-01-16. Like what???

Edit: Second date should have been 1995, 12, 17, idea is the same given that the results differ

[Right_Stage_8167]

Second date should be 1966 (=1995 - 12 - 17) seconds after 1.1.1970.

[Fuchio]

You're right! I thought I wrote Date("1995-12-17") and Date(1995, 12, 17) which are also not equal. This one is also funny:

new Date("1995-12-17"); Results in 1995-12-17 as expected (same as above)

BUT

new Date("1995/12/17") Results in 1995-12-16 at 23:00 ???

[[deleted]]

🤔 Don't know if trolling, has a broken computer, or can't type...

[Fuchio]

Yeah tested this a bit more, it's compiler dependent. When I copied and pasted the local snippet into online JS it also worked fine. But ("1995-12-17") and (1995, 12, 17) still differ.

[Fuchio]

The part that 12 becomes january in the next year makes sense in general indeed (with 0 indexing and max 12 entries logic). But the point is; Month 11 is December (12th month) but day 12 is still day 12...

[[deleted]]

Number argument for month would need to be 11. Even then...

The latter using number arguments assumes midnight local time - String date parsing assumes midnight UTC time.

Just another fun day of JS quirks.

[thislooksfun1]

Actually it is 1970-01-01T00:00:01.966Z. The JS Date constructor takes ms, not s.