All of IT in one image
-
I actually wish skateboards made a come back. Much more preferable over the escooters I see around a lot.
Yeah but no handle so you're much more likely to eat shit when you go down a slope or something.
-
This isn't the languages fault, it's the developers.
besides NaN actually being a number, this could completely and easily be avoided with typescript.
-
Yeah but no handle so you're much more likely to eat shit when you go down a slope or something.
Yea, it takes actual skill to use them ha ha
-
The Javascript literal interpretation of NaN never fails to amuse me.
"a"+"b" -> "ab" "a"-"b" -> NaN -
Guess why he came with a truck and not on a cargo bike...
Because you forgot to tell them that you already have the dependencies at home?
-
I'm no acupuncturist, but I'm pretty sure that it's SUPPOSED to say "naan minutes", which is time spent enjoying delicious Indian flatbread.
I guess you just eat your naan and then your ride arrives to ask you if you have any leftovers?
But what does that have to do with acupuncture?
-
NaN minutes later, a truck arrives in the alley, its license plate reads "undefined". Someone gets out of the vehicle
"I have something for you"
He gives you a package. You open it. It's an [object Object]"I've been looking for you! Got something I'm supposed to deliver. Your hands only."
-
This post did not contain any content.
Wait until Null opens the door
-
besides NaN actually being a number, this could completely and easily be avoided with typescript.
Naaah. Good programmers know how to use
as any as anyto make this work in typescript as well. -
Wait until Null opens the door
segmentation fault
-
"a"+"b" -> "ab" "a"-"b" -> NaNYeah:
parseInt("a") -> NoT a NuMbEr -
This isn't the languages fault, it's the developers.
I'm assuming by this you mean the developers of JS /s
-
Yeah:
parseInt("a") -> NoT a NuMbErSure, but the main issue here is that JS doesn't only auto cast to more generic but in both directions.
Maybe a better example is this:
"a" + 1 -> "a1" "a" - 1 -> NaNWith + it casts to the more generic string type and then executes the overloaded + as a string concatenation.
But with - it doesn't throw an exception (e.g. something like "Method not implemented"), but instead casts to the more specific number type, and "a" becomes a NaN, and NaN - 1 becomes NaN as well.
There's no situation where
"a" - "b"makes any sense or could be regarded as intentional, so it should just throw an error. String minus number also only makes sense in very specific cases (specifically, the string being a number), so also here I'd expect an error.If the programmer really wants to subtract one number from another and one or both of them are of type string, then the programmer should convert to number manually, e.g. using
parseInt("1") - parseInt("2"). -
This isn't the languages fault, it's the developers.
Albeit true, I want to note that some languages encourage such practices way more than others do. Also, when you've got a hammer everything looks like a
stringnail. -
This isn't the languages fault, it's the developers.
It's both.
-
You wouldn't want your code throw an exception
[object Object] -
As someone who mostly avoids JavaScript, I don't see the IT in this image, I just see a bad language I avoid!
I promise you, people make mistakes in every language lol.
-
This post did not contain any content.
I freaking love naan! Bring it!
-
I freaking love naan! Bring it!
NaN naan Jeremy that's insane
-
I got one of those too. I called the customer service to get another path home because of disturbances, and they just have robot answering. The robot started halfway through the call just reading pure json at me, and then said "to get this information as a message press 1" or something. This is what I got:
Here is your journey from undefined to undefined:
BUSS 506 towards Karolinska sjukhuset
09:36 from undefined
10:18 arrived at undefined.
Link to your journey.If you want those on separate lines you need to add two spaces on the end of each line!
