149
JavaScript is awesome
(jsdate.wtf)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Jul 2025
149 points (99.3% liked)
Programmer Humor
38555 readers
291 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
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?Parsing user input? Nonsense data coming from an API?
If you’re expecting shit data then you’d have unit tests for those cases so you’d know what to expect.
Maybe you don't expect shit data; you just get it. I know, always expect it....
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 Dateobject and check for that. Otherwise a randomNaNshows 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.
You think you'd get an error from the constructor.
Because this is a simplified example? Maybe you create the object in one place (saying something more realistic like "2015" or whatever your inexperience or AI told you to) and use getTime() at a later place where you thought you created it in a correct way.
User input is probably the big one where this API is gonna get stress-tested...
Because reasonable APIs have input validation provided out of the box, so that not everybody has to reinvent the validation wheel (inevitably incorrectly).