(saying something more realistic like “2015” or whatever your inexperience or AI told you to)
User input is probably the big one where this API is gonna get stress-tested...
(saying something more realistic like “2015” or whatever your inexperience or AI told you to)
User input is probably the big one where this API is gonna get stress-tested...
Hmm, I can believe that it was based on java.util.Date
, but I don't remember that being as unpredictable. I guess, a different API to begin with, would have avoided a lot of problems, though...
I'll let the hivemind know that we're supposed to have only one opinion.
On a definitely related note, I've recently been thinking it's wild how we build foot paths out of rocks and then put on rubber socks for actually walking on them.
In other words, asphalt is a scam by Big Foot to sell more shoes.
I imagine, they can still get inflamed gums or similar, if something gets stuck in there...
I believe, you have to take turns pushing down individual teeth. By random chance, it will close the mouth when you do that. So, you lose when you get bitten.
I'm always amazed how badly companies understand the concept of human interaction. Showing appreciation requires putting in some amount of effort. If you just type some words into a box and an image comes out, that's not anything. Might as well use the first clipart that comes up in image search...
I believe, you can basically turn it off in Firefox, by telling it to open new windows instead of tabs.
Might need to hide the tab bar via userChrome.css
, though...
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.