It's cool that Ruby has a === operator, but the fact that it is not a more strict version of == has caused me trouble in the past.

In TypeScript === is more strict, and when I go back and forth between Ruby and TS I have made a mistake in the past by putting a === when I intended a strict equality check.

I wonder if there is a linting setting where you can prevent your code base from ever using it.