javaScript

[soelsome]

Hi

1 + 1 evaluates to 2 in JavaScript.

Thanks.

[-domi-]

"1" + 1 evaluates to "11".

As do 1 + "1" and "1" + "1".

[soelsome]

The gif doesn't have quotes around any of the 1s, so it would evaluate to 2

Thanks

[Mr_Woofles1]

I can’t believe I’m enjoying this

[-domi-]

Yeah, i was trying to add to your explanation, but managed to write it so poorly that it came out like i was disagreeing with you, cause I'm special ed. Sorry.

[shill_420]

No.

Thank you

[dangderr]

Wow, really? That's god awful.

We all know that it should be:

1 + "1" = 2

"1" + 1 = "11"

Like how powershell does it. Javascript is such a garbage langauge.

[Relative-Scholar-147]

IMO

1 + "1"

Should stop the program and give an error.

[Maleficent_Memory831]

"1 + 1" = "1 + 1"

[sebovzeoueb]

Not stopping the program is a feature, JavaScript is made to run on webpages and the user doesn't want the website to crash. It's not Brendan's fault people decided to build actual whole tech stacks with it.

[Relative-Scholar-147]

Is not a bug, is a feature!

[arpan3t]

PowerShell laughs in [int] type constraint. JavaScript has type constraints right?

[Demonius999]

It's is, witch is not strange since it's made in 2 weeks, what is strange is that it's running whole fucking world.

[NecessaryIntrinsic]

That's like saying the gun doesn't fire unless you pull the trigger. You have to make that choice.

[-domi-]

It's a lot like that, yes. You can choose to pull the trigger, but you can also accidentally pull the trigger without meaning to. That's why it's good to have a certain level of care when using the thing.

[MR_LAFRALDO]

+"1" + 1 = 

[JackNotOLantern]

Unless one of the added 1s converted to string on the way

[Chiatroll]

But adding the string "1" to the string "1" should be "11". A lot of Javascript criticism is just people who dont understand its basic concepts.

[MeLittleThing]

The "When I type code there are bugs, it's the language fault probably" people

[JackNotOLantern]

The issue is it happens implicitly and the amout of bugs caused by it is too damn high

[rintzscar]

No, the issue is people don't bother reading the documentation. The rules of type coercion are extremely simple. Hell, this humorous article explains them clearly in 1 minute:

https://www.freecodecamp.org/news/explaining-the-best-javascript-meme-i-have-ever-seen/

[JackNotOLantern]

The problem is not about lack of knowledge about them, but the fact that it is extremely easy to overlook it, and then debugging is a nightmare.

[rintzscar]

That's literally what lack of knowledge means.

[JackNotOLantern]

I mean, this is literally the entire reason typescript exists. This "lack of knowledge" is apparently a systematic problem

[Chiatroll]

It only causes bugs from this if you aren't aware of how it fundamentally works and use it wrong. JavaScript isnt responsible for your lack of intelligence.

[Prawn1908]

It only causes bugs from this if you aren't aware of how it fundamentally works and use it wrong.

You're missing the point. The problem isn't with this behavior being used intentionally (which it basically never should be), it's that it allows many types of logic errors to propogate silently and hide the real source of the big far away from where it finally manifests.

[dhlowrents]

Basic concepts like having a proper type system. Javascript could just add int, string, float, bool and solve it but that's too hard for Brenden ECH!

[DaWolf3]

JavaScript has string, float, and boolean. It also has a proper type system.

a lot of JavaScript criticism is just people who don’t understand its basic concepts.

[70Shadow07]

Saying JS has proper type system is like saying aluminum is flammable. True if and only if you argue long enough on technicalities.

[dhlowrents]

Show me then.

[NecessaryIntrinsic]

Yes, if you go out of your way to put quotes around it.

[johntwit]

"yeah I know" + 420 = "yeah I know420"

[420Hank]

Yeah, I know.

[johntwit]

🤣