ITT: based languages

> original replies were talking about modern JS
> he posts of a truth table for "==" instead of "==="

Good job timmy.

Attached: but that's wrong 3.png (680x490, 266K)

>failing to see the irony of defending the need for type checking in a dynamically typed language
Weak dynamic typing was a mistake, and so was ECMAScript.

>Python
>sane language

> moving the goalpost

Attached: but that's wrong 2.png (680x624, 419K)

typescript

I'm not moving the goalpost, you are. You said "hurr durr modern JS uses === anyway" and I countered that by pointing out that dynamic typing is pointless if you need to do explicit type checking anyway.

>building a static typing system on top of a dynamic typing system
It's like trying to reattach a severed limb using staples and duct tape.

And it works

I wouldn't use it any other way.

So does Visual Basic or hacking in assembly, isn't really an argument of quality, is it?

I pointed out that the chart you posted wasn't relevant to modern JS. At no point did I take any position in this argument.

Everything after that was you trying to infer my own position from that, then responding as if I made any other argument besides pointing out that you didn't add anything useful to the discussion with your initial post.

Attached: but that's wrong 1.jpg (541x458, 79K)

>I pointed out that the chart you posted wasn't relevant to modern JS.
Literally how is it not?

Because if you type "==" it's not considered modern JS you absolute dingus.

Attached: homer am I disabled.jpg (1200x898, 110K)

1) Untrue.
2) See

>untrue
>he uses == in [current year]

Attached: came to laugh2.jpg (600x600, 29K)

Memes are poor substitute for arguments and facts.

The only use for loose equality check is checking for bottom values
expression == null evaluates to true if expression evaluates to either null or undefined

RealPlayer?

>loose equality checking
What kind of Orwellian hell is this? == used to be the equality operator and === used to be the identity operator, now they've retroactively renamed them to strong and loose equality checking? Double plus kek.

Also, as stated previously, but you JavaScript faggots seem to fail to understand:
=== is explicit type checking
If you require explicit type checking in a dynamically typed language, you're fucking doing it wrong.

fuck this is game of life

>The only use for loose equality check is checking for bottom values
Maybe monads fixed this

Gosh darn, I believe we have to scrap dynamically typed languages because the mighty Anonymous of Jow Forums wills it :(

Wow you still use R? Why don't you use Python? R is gone now.

>CTRL+F "holyc"
>0/0
cmon guys don't stray from the path of god

Dynamic strong typing is good. Dynamic weak typing is cancer.

this but unironically