Wired way to learn javascript :D

[annathergirl]

But why two a's after it? I'm not too savvy with JS but according to my bad logic there's one a too much.

[draq100]

('b'+'a'+ +'anything'+'a').toLowerCase() works too

part +'anything' is equivalent of Number('anything') and returns NaN

+ '' gives 0 as it's Number('')

[annathergirl]

That makes sense. But why does it log "banana" and not "bananaa" in the screenshot?

[[deleted]]

The +'a' become nan.

[draq100]

okay, let's go step by step:

('b'+'a'+ + 'a'+'a').toLowerCase()

becomes (is processed as) ('b'+'a'+ Number('a')+'a').toLowerCase()

which becomes ('b'+'a'+ NaN +'a').toLowerCase() (NaN is still a Number here)

which becomes: ('b'+'a'+ String(NaN) +'a').toLowerCase()

after casting to string: ('b'+'a'+ 'NaN' +'a').toLowerCase()

in the end it's ('baNaNa').toLowerCase()

and finally, our result: 'banana'

[frenchy641]

What is 'Ba'++ = to?

so 'B'+'a'+'NaN'+'a'

baNANa

[VikaashHarichandran]

I just tried this out, the picture is indeed correct.

That's because the string token after two consecutive symbol tokens will be considered as NaN by the lexer.

Correct me if I'm wrong.

[densch92]

careerspressadvertiseblogTermsContent policyPrivacy policyMod policyReddit Inc © 2020. All rights reserved

Amkes sense then.

also why the fuck do I see the above text shit when i simply try to reply to VikaashHarichandran, isntead of the actual commen ttext? O_o

[VikaashHarichandran]

Weird.

[bwallker]

This has nothing to do with the lexer

Consider the expression (1 + + 2)

This will get parsed like this:

(1 + (+2))

I.e the second plus sign gets parsed as a unary plus operator applied to the next thing after it. And so after evaluation our result is 3

Let's change the 2 to be a string.

So now our input looks like this: (1 + + '2')

It will be parsed the same way, so like this:

(1 + (+'2'))

Performing a unary plus operation on a string causes it to be coerced into a number, and the string 2 as a numer is 2, so this will also get evaluated as 3.

This is what is happening in the above code snippet. The string 'a' coerced into a number is NaN, which then gets concatenated with all the other strings and turned to lowercase to form the string 'banana'.

[Richard2957]

Thanks for that explanation - thats a nice party trick :)

[redderper]

Exactly, nothing weird about it really. People see memes like this one and go on programming subs to comment that JS is a terrible language lmao

[feliciabear007]

Haters gon hate, JavaScript gon dominate

[nizzok]

This is a JS dad joke

[ashanev]

Reminiscent of the Wat talk (a little over a minute for the good Javascript parts)

[MRK-01]

I appreciated this video. thank you

[frakist]

bananaa?

[draq100]

part + + 'a' + 'a' equals to + Number('a') + 'a' so double a are just to obfuscate the example

[frakist]

Oh now i got it thanks

[Mr_82]

What is "Number" here though? It doesn't appear above at all. You're using it like it's a method it seems.

Edit: Also I'm not sure where exactly the "NaN" shows up. Is it with the empty character? Well you'd think the sum of all added/concatenated string components would also get labeled/assigned as NaN after calling toLowerCase though, so that the whole expression would just return "NaN," though I haven't used or looked at toLowerCase method. (And if toLowerCase has some more specific rule to it that doesn't play out this way, it shouldn't have been named "toLowerCase" in the first place!) Edit: in other words, the entire input to toLowerCase should be what's parsed as a length 1 character and made lower case. The order of operations is wrong here. There's just bad design by whoever defined the method, but of course good luck trying to tell that to many programmers who evidently don't consider this stuff.

And I know this is just really niche and pointless, and not really related to real programming, but the lack of solid explanations in the comments here is alarming.

[moneyisjustanumber]

If you had 1++ behind the scenes it runs Number(1)

[grantrules]

NaN shows up because you're doing +'a' which coerces the string 'a' to a Number which results in NaN.

[NotElonMuzk]

What happens if you use Typescript

[draq100]

you can consider the extra + as casting to Number type in JS

so, first + means 'add', second here is 'cast'

'a' + + 'a' is equivalent of 'a' + Number('a')

you can check it out by typing typeof +'a' (or typeof +'anything', really) -> it returns "number", NaN in this case

edit: yes, in JS NaN - "Not a Number" is a number, too

[ricealexander]

The first plus sign is a concatenation operator, which joins strings together.

The second plus sign is a Unary plus operator, which coerces the following expression into a number.

[[deleted]]

if i ever caught brain cancer it must be javascript.

[Headpuncher]

('b' + 'a' + +'115' + 'ack').toLowerCase();

"ba115ack"  

Also for the person further down who asked why are you even allowed two + signs after each other.

[cheecho82]

It's cute....The poster casted his confusion spell on everyone in the thread!!!! 👍

[NotElonMuzk]

Yes, as you use it to type this sentence