Many JavaScript websites will advise you to never use the “==” and “!=” JavaScript operators, because when they compare variables containing different data types, JavaScript will coerce one of the operands to a matching type, sometimes in unexpected ways. We can thank the early days of JavaScript for this feature, when it was trying to be extraordinarily forgiving of sloppy code. I’m not going to list all the odd results that can arise from JavaScript’s operand coercion, because there are more than enough examples on the web already. To avoid unexpected type coercion, and thus unexpected matches and/or mismatches, the usual advice is to always use strict equality operators (“===” and “!==”). I disagree.

typeof OffscreenCanvas !== "undefined"

It's often a good idea to replace common primitives, such as strings, with appropriate value objects.

if (property === 'firstName')

In JavaScript, == is preferred to ===.

const div3 = n % 3 === 0; const div5 = n % 5 === 0;

It made sense when JS was doing small simple things in HTML - it doesn’t make much sense anymore

I have rarely encountered a good reason to use == in JS. Most of the time, or you are relying on it, you are probably doing something wrong.

Easier to just add a new operator that does things the right way and keep the original == operator as is. That way people can transition on their own time

typeof v === "number"

Lesson: use === and !==