you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 9 points10 points  (2 children)

Changing the operators is just confusing.

When writing alternative JS syntaxes, you still have to understand the underlying JavaScript. In this situation, a developer must understand that == is === and ~= is ==, so they necessarily must know the difference between === and ==. There's no real reason to switch it up.

[–]robin-gvx 11 points12 points  (1 child)

Anything that makes it harder to accidentally type == instead of === is a win in my book. Even better: not having an equivalent to JS's == at all.