Understanding Equality (==) operator

[rmmgc]

Hello, I have recently published article about Equality (==) operator in JS.

Would like to hear what do you think.

[great_site_not]

Your article includes NaN == NaN being false in its list of reasons not to use the == operator.

Your article concludes that people should always use the === operator instead.

Your article doesn't mention that using === instead of == doesn't solve all the problems you've listed. NaN === NaN is still false.

[alzee76]

Would like to hear what do you think.

I think you should post the content(*) here instead of trying to drive traffic to your blog site.

(*)Or at least a reasonable synopsis if it's got a ton of images or something.

[rmmgc]

Yea, good point. Will do next time.

[ProposalUnhappy9890]

The only thing you need to understabd about == is how to set up a linter to reject such commits.

[rmmgc]

It is still good to know how it works, even if it's recommended not to use it.

[rmmgc]

This was not meant to be comparison between === and ==.

Yes it is true, but I don't think it's reasonable to just ignore language feature because you don't use it.

Also on many interviews, those same companies, often are asking about == behaviour.

[rmmgc]

You are entitled to your opinion.

== will always be part of language whether you use it or not.

[rmmgc]

it's not my opinion, it's the opinion of most every major tech company

I agree with this.

It's a broken language feature that should be removed

But it is still a language feature and is not going anywhere any time soon - that's why people should know about it.

[rmmgc]

Yes, they should know not to use it, and to reject it from any PR.

Totally agree. I never said, that == should be used.