I don't see the benefit of this really, especially considering performance will probably be sub-par compared to strict equality and similar checks (e.g. using `val !== val` to check for `NaN`).
I still think === is the way to go in most of the cases. Object.is has an advantage when dealing with some numeric edge cases, but that's pretty much all. For the est, it's more verbose and less readable.