this post was submitted on 12 Jul 2025
145 points (98.7% liked)
Programmer Humor
37243 readers
78 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ok, I get that the Date API is problematic, but I wouldn't expect anything meaningfull from
new Date("not a date").getTime()
anyway. Why would you in the first place?It's mainly horrid, because it means you have to code extremely defensively (or I guess, use a different API).
You can't rely on
new Date("not a date")
aborting execution of your function by throwing an error. Instead, you have to know that it can produce anInvalid Date
object and check for that. Otherwise a randomNaN
shows up during execution, which is gonna be extremely fun to try to find the source of.I understand that it's implemented like that partially for historical reasons, partially because it's often better to display "NaN" rather than nothing, but it's still the sort of behavior that puts me in a cold sweat, because I should be memorizing all kinds of Best Practices™ before trying to code JavaScript.